Re: [Fontforge-devel] Current source tarball

[Peter B. <ps...@vi...>]

Stepan Roh wrote:

> Hello.
>
> On Tue, 15 Nov 2005, George Williams wrote:
>
>> On Tue, 2005-11-15 at 08:29, Peter Baker wrote:
>>
>>> Is something wrong with the current source tarball
>>> (fontforge_full-20051103.tar.bz2)? When I try to untar it (xjvf) I get
>>>
>>> tar: This does not look like a tar archive
>>> tar: Skipping to next header
>>> tar: Archive contains obsolescent base-64 headers
>>> tar: Error exit delayed from previous errors
>>
>> Nope, nothing wrong with it. Just a different format. You now need to
>> say
>>
>> $ bunzip2 fontforge_full-20051103.tar.bz2
>> $ tar xf fontforge_full-20051103.tar
>
>
> The 'j' option in xjvf is for use of bzip2 (at least on Slackware).
>
> Have a nice day.
>
> Stepan Roh


Well, that's what puzzled me: I used the j option, as I have all along. 
It didn't work this time. But never mind: if it's working for other 
people there must be something wrong with my tar.

Peter