On Mon, 16 May 2011 08:51:00 -0500 Jonathan Nieder wrote: > Package: apt-listbugs > Version: 0.1.4 > Severity: important > > Hi,
Hi Jonathan,
thanks for your bug report!
>
> New armel squeeze system, running through qemu.
Taking into account your self-reply, I take notice that what you are
talking about is actually a new armel _wheezy_ system.
> After installing
> apt-listbugs from unstable, I decided it's time to upgrade everything
> to experimental. So I told cupt to do so ("cupt full-upgrade").
Please note that Cupt is not really fully tested with apt-listbugs (at
least as far as I know): hence you should not take for granted that it
will work flawlessly with apt-listbugs.
That being said, it may well be that the bug you are experiencing does
*not* depend on the use of Cupt.
Please try to reproduce the bug outside of the package manager.
For instance, does apt-listbugs work for you if you just issue the
following command?
$ apt-listbugs list apt
Reading package fields... Done
Reading package status... Done
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
grave bugs of apt (0.8.14.1 -> ) <unfixed>
#407511 - apt: Wrong value for APT::Default-Release may cause unwanted
#625447 - apt-cdrom does not add CD at all; ignores drive
serious bugs of apt (0.8.14.1 -> ) <unfixed>
#558784 - apt: re-adds removed keys
Summary:
apt(3 bugs)
>
> 6 new packages were to be installed, 45 upgraded, and 1 removed.
> The result:
>
> Reading package fields... 0% ... E: private method `chomp!' called for
> nil:NilClass
> E: 'dpkg 'pre' action '/usr/sbin/apt-listbugs apt || exit 10'' failed: exit
> code '10'
It seems that, at /usr/share/apt-listbugs/apt-listbugs/logic.rb:770 ,
the `chomp!' method is called for a nil object.
Hence, it seems that pkgnames[index] is nil, for some reason.
I must investigate further, to understand what's going on on your
system.
Needless to say, on my amd64 and i386 (testing) systems and on my sid
chroot, apt-listbugs works fine with aptitude. As a consequence, it
could be something caused by Cupt, or maybe some architecture-specific
issue.
>
> $ ruby --version
> ruby 1.8.7 (2011-02-18 patchlevel 334) [arm-linux-eabi]
I have
$ ruby --version
ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux]
here...
>
> Any hints for tracking this down?
This is going to be tricky.
I can try to reproduce the bug on a sid chroot (on amd64) with Cupt,
but unfortunately I don't have any armel system where I can investigate
a possible architecture-specific bug. And I lack qemu expertise to
setup an emulated armel system... :-(
Anyway, I am afraid you'll have to wait some time, since I am quite
busy in these days.
Sorry... :-(
P.S.: Note to self: I see there has been an old bug (#289361) about a
`chomp!' invoked for a nil object; I must check whether it is a relative
of the present bug...
--
http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt
New GnuPG key, see the transition document!
..................................................... Francesco Poli .
GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpzC5rq7OpsN.pgp
Description: PGP signature
