On Sun 03 Jun 2018 at 11:33:17 +0200, tlaronde%polynum.com@localhost wrote:
> tar: File extended headers posix ustar archive. Extracting as plain
> files. Following files might be in the wrong directory or have wrong
> attributes.
I started noticing that when I was building some more packages from the
then-latest stable pkgsrc branch (2018Q1).
The weird thing is that packages built earlier in by rebuild process
didn't have this problem. The ones built after a (un?) certain point do
have the problem.
I tried this:
ls -tr /scratch/packages.amd64-7.0-gcc49/All > /tmp/file
while read file ; do echo $file; tar tvfz "/scratch/packages.amd64-7.0-gcc49/All/$file" 2>&1 ; done < /tmp/files | more
and it seems the oldest tar file that elicits the message "tar: File
extended headers posix ustar archive...." is pkg_install-20180325.tgz.
The one before is pkg_chk-2.0.9.tgz. The gtar archive hasn't been built
yet at that time!
-rw-r--r-- 1 root wheel 14901 Apr 15 11:34 pkg_chk-2.0.9.tgz
-rw-r--r-- 1 root wheel 961906 Apr 15 11:38 pkg_install-20180325.tgz
-rw-r--r-- 1 root wheel 1031231 Apr 15 15:40 gtar-base-1.30.tgz
From pkg_install-20180325.tgz on, the packages seem to elicit the
message. (I didn't automate the check if this was true for 100% of them,
though).
pkg_install includes pkg_create, which would create the tar files. So I
guess the culprit is there.
-Olaf.
--
___ Olaf 'Rhialto' Seibert -- Wayland: Those who don't understand X
\X/ rhialto/at/falu.nl -- are condemned to reinvent it. Poorly.
Attachment:
signature.asc
Description: PGP signature