tar contains unknown extended header keywords

[GoogleCodeExporter]

What steps will reproduce the problem?
1. tar xf nose-1.1.2.tar.gz on Mac OSX 10.6 with fink tools
2. using tar (GNU tar) 1.26

What is the expected output? What do you see instead?

Expect it to just untar.  I'm getting this:

tar xf /sw/src/nose-1.1.2.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'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'

What version of the product are you using? On what operating system?

Please provide any additional information below.

This doesn't hurt anything as far as I can tell, but might freak some people 
out.

Original issue reported on code.google.com by schw...@gmail.com on 2 Aug 2011 at 12:37

[GoogleCodeExporter]

I don't see those errors using tar on Mac OS X Snow Leopard (I think the 
standard one from Developer Tools). 

$ tar --version
bsdtar 2.6.2 - libarchive 2.6.2

btw, this file was created by standard Python distutils and I think most people 
will use pip to install nose.  Marking as invalid but feel free to re-open if 
you find something that could prevent installation or make installation extra 
confusing.

Original comment by kumar.mcmillan on 2 Aug 2011 at 8:08

• Changed state: Invalid

[GoogleCodeExporter]

I have this problem as well on Scientific Linux 5.5.

(env)[pdaq@i3live tar]$ tar xzf nose-1.1.2.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'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Error exit delayed from previous errors
(env)[pdaq@i3live tar]$ tar --version
tar (GNU tar) 1.15.1
(env)[pdaq@i3live tar]$ 

Since the returned error code is nonzero, this breaks various install scripts.  
I am running in a context where PIP / pypi are not directly available (this is 
on a machine with limited internet accessibility), so this has real 
consequences.  Thanks!

Original comment by eigenhom...@gmail.com on 22 Dec 2011 at 9:28

[GoogleCodeExporter]

This is a result of using BSD tar rather than GNU tar to create the tar file. 
Please repackage the tarball with GNU tar by building the dist on Linux.

Original comment by nug...@gmail.com on 1 Mar 2012 at 6:15