Date: Tue, 29 May 2007 19:03:40 -0700 From: Colin Percival <cperciva@freebsd.org> To: Steven Hartland <killing@multiplay.co.uk> Cc: John-Mark Gurney <gurney_j@resnet.uoregon.edu>, freebsd-stable@freebsd.org Subject: Re: bug in BSD tar? Message-ID: <465CDB7C.5010504@freebsd.org> In-Reply-To: <004601c7a257$09cc58f0$b6db87d4@multiplay.co.uk> References: <465B9BA3.30905@freebsd.org> <00fe01c7a1de$aff18080$b6db87d4@multiplay.co.uk> <20070529231536.GA4602@funkthat.com> <004601c7a257$09cc58f0$b6db87d4@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Steven Hartland wrote: > ----- Original Message ----- From: "John-Mark Gurney" > <gurney_j@resnet.uoregon.edu> >> 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? > > The file is correct when extracted but gtar is, as you say, throwing > an error because of the tar format. The exit error is the issue as in > a scripted environment, as we have, the error causes the failure of the > whole operation. GNU tar is broken. POSIX specifically allows for vendor extensions (such as the SCHILY.* extensions which were introduced by star), and the correct way to handle them is by printing a warning message, ignoring the extension, and not treating it as an error. You can work around gtar's breakage by explicitly telling it to ignore these options via --pax-option="delete=SCHILY.*" . Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?465CDB7C.5010504>