Bug #1541
closedtar(1) fails to extract a valid archive
0%
Description
https://www.mirbsd.org/MirOS/dist/hosted/kwalletcli/kwalletcli-1.00.tar.gz
$ tar -zxf kwalletcli-1.00.tar.gz
tar: Unrecognized archive format
tar: Error exit delayed from previous errors.
$
Using g(un)zip(1) and tar(1) works:
$ gzip -cd kwalletcli-1.00.tar.gz | tar -xf -
$
Updated by jgordeev about 15 years ago
The file unpacks OK here on DragonFly 2.2.
The MD5 digest of the file I used for testing is
76ef3c1d611a11ea13dc805d67d82208.
Updated by dillon about 15 years ago
:Hasso Tepper (via DragonFly issue tracker) wrote:
:> New submission from Hasso Tepper <hasso@estpak.ee>:
:>
:> https://www.mirbsd.org/MirOS/dist/hosted/kwalletcli/kwalletcli-1.00.tar.gz
:>
:> $ tar -zxf kwalletcli-1.00.tar.gz
:> tar: Unrecognized archive format
:> tar: Error exit delayed from previous errors.
:> $
:>
:> Using g(un)zip(1) and tar(1) works:
:>
:> $ gzip -cd kwalletcli-1.00.tar.gz | tar -xf -
:> $
I get the same thing. I ktrace'd it and it looks like bsdtar
is trying to examine the gzip header itself... and clearly
making a mistake.
If I gunzip | gzip > x.tar.gz and then tar tvzpf x.tar.gz, that
works, so basic recognition of gzip files is working properly in
tar. It just doesn't recognize THAT particular gzip file.
So it must be a bug in libarchive somewhere, or perhaps it simply
does not properly recognize gzip formats?
-Matt
Matthew Dillon
<dillon@backplane.com>
Updated by polachok about 15 years ago
bsdtar 2.7.1/libarchive 2.7.1 works for me on linux. We have 2.7.0 on DragonFly.
Updated by hasso about 15 years ago
Good catch, bsdtar 2.7.1 changelog contains this line as well amongst
others: "Handle gzip files signed with OpenBSD "gzsig" program." That's
probably it.