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

From: matthew green <mrg@eterna.com.au>
To: christos@zoulas.com (Christos Zoulas)
Cc: gnats-bugs@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org
Subject: re: bin/30132: Something is wrong with tar(1) --chroot 
Date: Thu, 05 May 2005 10:44:54 +1000

    
    you need to specify --insecure to extract those files. It is dubious if
    --chroot should imply --insecure so I did not do it.
 
 
 i don't think this is the correct answer.  the tarballs that are failing
 to extract are netbsd sets.  afaik, those all have files that start with
 "./" in them.  to me this implies that whatever tests you have added for
 checking extraction has not changed location are broken in the precense
 of the --chroot flag.
 
 surely you aren't suggesting that sysinst needs to pass --insecure?
 
 
 .mrg.