The following reply was made to PR bin/30132; it has been noted by GNATS.

From: Juan RP <juan@xtrarom.org>
To: gnats-bugs@netbsd.org
Cc: christos@zoulas.com
Subject: Re: bin/30132: Something is wrong with tar(1) --chroot
Date: Thu, 5 May 2005 15:03:52 +0200

 On Thu,  5 May 2005 12:55:02 +0000 (UTC)
 christos@zoulas.com (Christos Zoulas) wrote:
 
 >  I thought that they start with / not ./ reading from the output of tar.
 >  Are you sure that they start with ./?
 
 You can create a tarball with files starting with ./ or /, they will fail to
 unpack with the new code, example:
 
 [juan@Nocturno][~/foo]> tar cvpzf xtar.tgz xtar 
 xtar
 xtar/xtar.o
 xtar/xtar.c
 xtar/xtar.h
 xtar/.gdbinit
 xtar/xtar
 xtar/Makefile
 tar: ustar vol 1, 7 files, 0 bytes read, 174080 bytes written in 1 secs
 (174080 bytes/sec)
 [juan@Nocturno][~/foo]>
 
 As you can see here, this tarball has the files starting with ./, but it fails
 to unpack when using --chroot.
 
 Same goes when the tarball has the files starting with / (but that's ok).