Re: bug in BSD tar?

Steven Hartland wrote this message on Tue, May 29, 2007 at 11:46 +0100:
----- Original Message -----
From: "Colin Percival" <cperciva@xxxxxxxxxxx>
----- Original Message ----- From: "Colin Percival" <cperciva@xxxxxxxxxxx>
tar -xvzf test.tar.gz
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
cantiquedeno\353l1_loop.wav
tar: Error exit delayed from previous errors

This looks like fairly typical symptoms of gnutar being broken. What
makes you think that the archive created by BSD tar was invalid?

As a filename should have no bearing on what extended headers
are set.

Why not? In this case, bsdtar is detecting that the file name contains
non-7-bit-ascii characters and is emitting a pax header for that reason;
and since it can't suppress the pax header entirely, it goes ahead and
emits the "not vital but potentially useful" headers for the device #,
inode #, number of links, and high precision timestamps.

I still see no evidence that bsdtar is doing anything wrong.

I suppose this then comes down to the fact that gnu tar is the prevalent
version out there and as such with BSD creating archives which are
incompatible with that leads to problems. From our side we'll have to
switch to using gnutar until this issue is resolved as we need to ensure
compatibility.

Is the file incorrect when extracted? or is this a mater of gtar throwing
an error because of the tar format, and an option to bsdtar could be provided
to change the output tar format?

--
John-Mark Gurney Voice: +1 415 225 5579

"All that I will do, has been done, All that I have, has not."
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: bug in BSD tar?
    ... tar: Ignoring unknown extended header keyword `SCHILY.dev' ... makes you think that the archive created by BSD tar was invalid? ...
    (freebsd-stable)
  • Re: bug in BSD tar?
    ... tar: Ignoring unknown extended header keyword `SCHILY.dev' ... I still see no evidence that bsdtar is doing anything wrong. ...
    (freebsd-stable)
  • Re: bug in BSD tar?
    ... tar is creating invalid archives which when handed to gnutar to ... Ignoring unknown extended header keyword `SCHILY.dev' ... This looks like fairly typical symptoms of gnutar being broken. ...
    (freebsd-stable)
  • Re: bug in BSD tar?
    ... tar: Ignoring unknown extended header keyword `SCHILY.dev' ... makes you think that the archive created by BSD tar was invalid? ...
    (freebsd-stable)
  • Request for Comments: libarchive, bsdtar
    ... Add "libarchive" to the tree, ... tar command to "bsdtar" once it is sufficiently stable. ... gnutar or continuing to use gnutar under a different name. ...
    (freebsd-arch)