On May 5, 10:44am, mrg@eterna.com.au (matthew green) wrote:
-- Subject: re: bin/30132: Something is wrong with tar(1) --chroot

| 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?

I thought that they start with / not ./ reading from the output of tar.
Are you sure that they start with ./?

christos