maemo.org Bugzilla – Bug 3033
Diablo BusyBox v1.6.1 has broken tar
Last modified: 2009-03-24 17:29:17 UTC
You need to
before you can comment on or make changes to this bug.
OS2008 / 2.2007.50-2
STEPS TO REPRODUCE THE PROBLEM:
1. wget http://www.mpfr.org/mpfr-2.3.1/mpfr-2.3.1.tar.gz
2. tar xzf mpfr-2.3.1.tar.gz
The archive should be untar'ed.
I get the following error:
tar: invalid tar magic
always with this archive, no problem with some other archives. Decompressing
the archive first (with gunzip) and using "tar xf mpfr-2.3.1.tar" does not
solve the problem.
On a Debian machine, I got the same problem with Debian's busybox package
(using an even older version), but no problem with BusyBox 1.9.1 from upstream.
So, I assume that an upgrade would fix the problem.
I can confirm this still happens for some archives i try and the one linked
Nokia-N800-51-3:~# cat /etc/osso_software_version
Confirmed, thanks for the report!
(In reply to comment #0)
> On a Debian machine, I got the same problem with Debian's busybox package
> (using an even older version), but no problem with BusyBox 1.9.1 from
> upstream. So, I assume that an upgrade would fix the problem.
Unfortunately the Busybox version isn't going to be updated yet for the next
release, hopefully for the one after that.
> SOFTWARE VERSION:
> OS2008 / 2.2007.50-2
(In reply to comment #1)
> I can confirm this still happens for some archives i try and the one linked
> above also.
> SOFTWARE VERSION:
This quick-fix release fixed just the booting issue, AFAIK it didn't have
any changes to the rootfs (where the device Busybox resides).
Busybox will be updated for the next major release (Fremantle).
Looks like provided archive is older format archive (V7) which was created
using --format=v7 (--portability,--old-archive).
(In reply to comment #4)
> Looks like provided archive is older format archive (V7) which was created
> using --format=v7 (--portability,--old-archive).
It was built by GNU tar via "make dist" (automake version was 1.9.6). It seems
that --format=v7 is the default used by automake.
Fix will be released in next public Diablo release / SSU update.
Fixed in package
which is part of the internal build version
Any public update released with or after this build version will include the
Please verify that the new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.
Note that this fix is not included in today's 4.2008.36-5 update.
Fix for this should be included in today's 5.2008.43-7 SSU update.
Please verify the fix by marking this bug report as VERIFIED if you have some
Busybox config-deb file change in busybox 3:1.6.1.legal-1osso16:
Looks good to me in 43-7 , but I'm not the original reporter ;)
OK on the same tar file.
Fremantle alpha busybox is built with CONFIG_FEATURE_TAR_OLDSUN_COMPATIBILITY
(new option) but not CONFIG_FEATURE_TAR_OLDGNU_COMPATIBILITY and again fails to
process the mpfr-2.3.1.tar.gz archive.
Lucas: So this was FIXED for Diablo 4.1.3 but is still a VALID bug for Busybox
1.10.2 in Fremantle SDK alpha?
Yes, I guess the option slipped through the cracks.
(In reply to comment #14)
> Lucas: So this was FIXED for Diablo 4.1.3 but is still a VALID bug for Busybox
> 1.10.2 in Fremantle SDK alpha?
It would be better to have a separate bug because this bug was fixed in Diablo,
for the Diablo version of Busybox and the new bug is in Fremantle, in the
Fremantle version of Busybox...
Cloned as bug 4237 for Fremantle.
Closing this one.