On Sun, Apr 27, 2014 at 11:57:49PM +0100, peter green wrote: > Package: unar > Version: 1.1-2 > Severity: important > x-debbugs-cc: debian-...@lists.debian.org > > I recently got the following report from a raspbian wheezy user > (https://bugs.launchpad.net/raspbian/+bug/1165466). > > > >Using the simple test file found at > >http://www.maximumcompression.com/data/files/text-test.rar > ><http://www.maximumcompression.com/data/files/text-test.rar>: > > > >"unar text-test.rar" and "lsar text-test.rar" raise the error: > > > >"text-test.rar: RAR > >Archive parsing failed! (Unknown error.)" > > > >unar on my Squeeze desktop happily extracted the above archive. > > > So I decided to test it in some test chroots (note: the i386 chroot > was on an amd64 host, the arm chroots were all on an armv7 host) > > debian wheezy i386: works > debian wheezy armel: fails > debian wheezy armhf: fails
wheezy armhf works fine with that test file for me. Both lsar and unar worked. > debian jessie armel: fails Worked fine in a chroot for me. > debian jessie armhf: fails Worked fine in a chroot for me. > raspbian jessie: fails > > So it looks like a general arm breakage, not something specific to raspbian. No, I don't think so. What system did you run your test on? I tested on a couple of different Cortex-A15 systems. Perhaps the ObjC runtime library has accidentally picked up some CPU dependancy it wasn't supposed to. You could try running 'strace' on the lsar or unar, and perhaps it would give a clue what it was doing when it got the unknown error. Unfortunately the code which prings 'Archive parsing failed' is in ObjC, which I don't usually deal with, so parsing what it does takes some time (ObjC is in interesting but certainly different language). -- Len Sorensen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
