Subject: bin/25211: NetBSD-1.6.2/source/sets/xsrc.tgz unpacks to two directories, xsrc and xfree
To: None <>
From: None <>
List: netbsd-bugs
Date: 04/17/2004 15:55:51
>Number:         25211
>Category:       bin
>Synopsis:       NetBSD-1.6.2/source/sets/xsrc.tgz unpacks to two directories, xsrc and xfree
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Apr 17 13:57:00 UTC 2004
>Release:        NetBSD 1.6.2
System: NetBSD charlie 1.6.2 NetBSD 1.6.2 (GENERIC) #0: Tue Feb 10 23:52:52 UTC 2004 macppc
Architecture: powerpc
Machine: macppc
	This probably also affects other versions.

	When unpacking source/sets/xsrc.tgz (MD5 (xsrc.tgz) = e52572e7f911ca5952d025a2689760a9) in /usr *with tar*, in addition to /usr/xsrc, the directory /usr/xfree is also created.

	This is probably the real cause of NetBSD Problem Report #15491, which apparantly has been closed because the real error was not discovered then.

easy:../sets $ pax -z -f xsrc.tgz |grep -v ^xsrc
easy:../sets $ tar ztf xsrc.tgz |grep -v ^xsrc   

	The tar used is /usr/bin/tar (GNU tar version 1.11.2)
	pax is /bin/pax

	Unpack xsrc.tgz with tar
	Well, the obvious workaround:
	Unpack xsrc.tgz with pax

	However, something which is presumably a tar archive *should* unpack correctly with tar, IMHO.

	Perhaps when creating archives, tar ztf should be used to verify that correct unpacking with tar is possible.

	As I seem to have succesfully re-packed the unpacked xsrc with tar, this is probably indicative of a bug in how pax (presuming pax was originally used to make the archive) creates tar files. I know next to nothing about different tar formats, so if the problem is related to GNU tar being non-standard, so be it. I still think a .tar.gz or .tgz file should unpack correctly with tar, though.