Russ Allbery <[email protected]> hat am 24. Dezember 2009 um 20:42 geschrieben:
> tags 558360 unreproducible moreinfo > thanks > > Sebastian Krysmanski <[email protected]> writes: > > > When I'm running lintian on a certain custom built .deb package > > (ghostscript_8.64-5_i386.deb) then lintian sometimes just fails without > > any error message with error code 141. > > > $ lintian --check --allow-root --show-overrides -i -b > >ghostscript_8.64-5_i386.deb >lintian.txt > > > > $ echo $? > > 141 > > > In this case "lintian.txt" is empty. However, sometimes (every thrid > > attempt or so) lintian works on this package. The deb package was built > > using cowdancer. I've uploaded it here: > > http://www.mayastudios.com/ghostscript_8.64-5_i386.deb > > I can't duplicate this problem with either lintian 2.2.18 or the current > development version on a Debian host using that same package. This is not > something that Lintian is doing intentionally, so in order to track this > down further we'd need either debugging output or some way to reproduce > it. Gladly, but I'm not quite sure how and what to provide as debugging output. For starters I've run lintian (2.2.18 this time) with the "-d" switch: $ lintian --check --allow-root --show-overrides -i -b -d ghostscript_8.64-5_i386.deb N: Lintian v2.2.18ubuntu1 N: Lintian root directory: /usr/share/lintian N: Configuration file: /etc/lintianrc N: Laboratory: N: Archive directory: N: Distribution: N: Default unpack level: 1 N: Architecture: any N: ---- N: Setting up lab in /tmp/VIcPpbdtdw ... Return code is still 141. The content of the lab directory is: $ ll /tmp/VIcPpbdtdw/* /tmp/VIcPpbdtdw/binary: total 0 /tmp/VIcPpbdtdw/info: total 0 -rw-r--r-- 1 root root 0 Dec 25 10:50 binary-packages -rw-r--r-- 1 root root 0 Dec 25 10:50 source-packages -rw-r--r-- 1 root root 0 Dec 25 10:50 udeb-packages /tmp/VIcPpbdtdw/source: total 0 /tmp/VIcPpbdtdw/udeb: total 0 I've also tried to run lintian with a non-root user and with fewer parameters: #lintian --check -b -d ghostscript_8.64-5_i386.deb but with the same result. > > > Btw: I know I'm using Ubuntu (9.10) but I don't think this is a Ubuntu > > specific error. If someone using Debian could just check whether this > > problem appears at his/her system as well it'll be nice. > > I'm curious if the problem would disappear if you upgraded to the latest > Ubuntu Lintian package. > Problem is still present in version 2.2.18 (see above). > -- > Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>
