I was wondering, should this be considered a bug? It's clear that tar is being called with no gunzip argument, and then it's trying to identify the magic number to continue if true for tar file.
Since busybox is supposed to be small and fast, is this kind of error supposed to get handled? Marcus Diniz On Dec 21, 2015 20:12, "Heinrich Schuchardt" <[email protected]> wrote: > OpenWRT ChaosCalmer uses busybox 1.23.2. > > For many tar.gz files I receive errors like: > > user@MR3020:~/src$ wget http://tukaani.org/xz/xz-5.2.2.tar.gz > user@MR3020:~/src$ tar -xzf xz-5.2.2.tar.gz > tar: invalid tar magic > user@MR3020:~/src$ tar: write: Broken pipe > > GNU tar on Debian Jessie amd64 has no problem with the same file. > > Best regards > > Heinrich Schuchardt > _______________________________________________ > busybox mailing list > [email protected] > http://lists.busybox.net/mailman/listinfo/busybox >
_______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
