A tar file file created by:
bsdtar 3.3.2 - libarchive 3.3.2 zlib/1.2.11 liblzma/5.2.3
bz2lib/1.0.6 on FreeBSD-current-12
can be unpacked en-mass by bsdtar 2.7.0 - libarchive 2.7.0 on FreeBSD 8
but it can not unpack a single file or directory on its own (in any
format).
(On FreeBSD 8.0.. file created on -current)
$ tar xzvf test.pax -C /tmp/unpack2
root
x ./root/
x ./root/sqliterc: (Empty error message)
tar: Error exit delayed from previous errors.
$ tar xzvf test.tgz -C /]mp/unpack2 root
x ./root/
x ./root/sqliterc: (Empty error message)
tar: (Empty error message)
tar: Error exit delayed from previous errors.
or, with a differnet error message..
mesh-upgrade# tar xzf ./CloudController_full_7.2.0.0.12910.tgz -C /mnt/tmp/upgrade-data --strip=1 etc/AWS-Platform etc/p8.conf root/pre-upgrade-resources
|
p8.conf: Line too long
|
tar: root/pre-upgrade-resources: Not found in archive
|
|
tar: Error exit delayed from previous errors.
|
a file with the same contents, created with:
bsdtar 3.2.2 - libarchive 3.2.2 zlib/1.2.8 liblzma/5.2.2 bz2lib/1.0.6
running from FreeBSD 10/stable can be correctly extracted, both as a whole set, or as individual items.:
The question is: what is the difference in the file?
also, the file from 12 can have a file extracted by the tar in freebsd
10.3 (same as above)..
works as expected.. same file.
any thoughts?
maybe due to 64 bit inode numbers change???
sometimes the error is "line too long" and sometimes ("Empty error message)"