tags 626937 + unreproducible
quit

Hi Francesco,

Thanks for your reply.

Francesco Poli wrote:

> Please note that Cupt is not really fully tested with apt-listbugs (at
> least as far as I know)

I've been using apt-listbugs with cupt on amd64 for a while, for what
it's worth.

> 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 <package> worked okay for me when I tried it in the
course of investigation.

The bad news: before receiving your reply, I uninstalled apt-listbugs,
ran "cupt dist-upgrade", and reinstalled apt-listbugs, and now the
problem doesn't happen anymore.  I think it must have had something to
do with the particular wheezy -> experimental upgrade that was being
proposed[1].

> 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.

I doubt it is architecture-specific, unless there is some assumption
of signed char somewhere or something like that.  This is an
interpreted language and it wasn't a segfault. :)  To reproduce the
slow way (I don't encourage this --- it's just for illustration):

 1. unset MALLOC_PERTURB_, to avoid running afoul of Bug#626875.
 2. Follow the instructions from that bug log to get a wheezy
    image.  Or just grab Aurélien's squeeze image from
    http://people.debian.org/~aurel32/qemu/armel/ and upgrade it.
 3. Install apt-listbugs and cupt.
 4. Put sid and experimental in sources.list.  Put

        APT::Default-Release "experimental";
        cupt::worker::defer-triggers "1";

    in a file in /etc/apt/apt.conf.d/.
 5. Run "cupt update".
 6. Run "cupt full-upgrade".

> Anyway, I am afraid you'll have to wait some time, since I am quite
> busy in these days.
> Sorry...   :-(

I don't mind; just thought the report might be useful to someone.
Sorry, I should have used btrfs and taken a snapshot before upgrading.
Next time.

http://ruby-doc.org/core/classes/String.html tells me:

| String objects may be created using String::new or as literals.
|
| Because of aliasing issues, users of strings should be aware of the
| methods that modify the contents of a String object. Typically,
| methods with names ending in ``!’’ modify their receiver, while those
| without a ``!’’ return a new String. However, there are exceptions,
| such as String#[]=.

I wonder if apt-listbugs/logic.rb, line 770 should not be

        pkgnames[index] = pkgnames[index].chomp

and similarly for "if line != nil" on line 1169?  Though that wouldn't
affect this bug.

pkgnames gets populated by adding entries of the form

        filename = line.split(" ")[4]

after apt-listbugs sees a blank line.  If there are 4 or fewer fields
on such a line then filename will be nil.  Perhaps cupt mentioned a
package it was going to remove or trigger in a nonstandard way.

Is the apt VERSION 2 hook interface documented anywhere?  I tried
"man apt" and "man apt.conf" but no luck so far.

Thanks for your thoughtfulness,
Jonathan

[1] Judging from dpkg.log, that looks like

 bsdutils       1:2.17.2-9.1 → 1:2.19.1-1
 debianutils    3.4.4 → 3.4.5
 libreadline6   6.1-3 → 6.2-1
 zlib1g 1:1.2.3.4.dfsg-3 → 1:1.2.5.dfsg-1
 libk5crypto3   1.9+dfsg-1+b1 → 1.9+dfsg-1+moonshot1
 initramfs-tools        0.98.8 → 0.99
 liblzma2       5.0.0-2 → 5.1.0alpha+20110206-1
 libgnutls26    2.10.5-1+b1 → 2.12.5-1
 libgcrypt11    1.4.6-5 → 1.5.0~beta1-1
 busybox        1:1.17.1-10 → 1:1.18.4-2
 sysvinit       2.88dsf-13.2 → 2.88dsf-13.5
 libdb5.1       5.1.25-1 → 5.1.25-10
 readline-common        6.1-3 → 6.2-1
 libss2 1.41.12-4 → 1.41.14-1
 sysv-rc        2.88dsf-13.2 → 2.88dsf-13.5
 dash   0.5.5.1-7.4 → 0.5.6.1-1~exp2
 libcomerr2     1.41.12-4 → 1.41.14-1
 linux-image-2.6-versatile      2.6.38+33 → 2.6.38+34
 grep   2.6.3-3 → 2.7-2
 libuuid1       2.17.2-9.1 → 2.19.1-1
 libblkid1      2.17.2-9.1 → 2.19.1-1
 gcc-4.4-base   4.4.6-2 → 4.4.6-3
 xkb-data       2.1-2 → 2.2.1-1
 findutils      4.4.2-1+b1 → 4.5.10-1
 traceroute     1:2.0.15-1 → 1:2.0.17-1
 installation-report    2.44 → 2.45
 sysvinit-utils 2.88dsf-13.2 → 2.88dsf-13.5
 mount  2.17.2-9.1 → 2.19.1-1
 libboost-iostreams1.46.1       1.46.1-4 → 1.46.1-5
 perl   <none> → 5.12.3-6
 perl-modules   <none> → 5.12.3-6
 xz-utils       5.0.0-2 → 5.1.0alpha+20110206-1
 util-linux     2.17.2-9.1 → 2.19.1-1
 libudev        167-3 → 168-2
 udev   167-3 → 168-2
 e2fslibs       1.14.12-4 → 1.41.14-1
 e2fsprogs      1.14.12-4 → 1.41.14-1
 console-terminus       4.30-2 → <none>
 console-setup-linux    <none> → 1.73
 console-setup  1.70 → 1.73
 keyboard-configuration 1.70 → 1.73
 libswitch-perl <none> → 2.16-1
 libclass-isa-perl      <none> → 0.36-1
 libpod-plainer-perl    <none> → 1.03-1
 libkrb5support0        1.9+dfsg-1+b1 → 1.9+dfsg-1+moonshot1
 libkrb5-3      1.9+dfsg-1+b1 → 1.9+dfsg-1+moonshot1
 libgssapi-krb5-2       1.9+dfsg-1+b1 → 1.9+dfsg-1+moonshot1
 gcc-4.6-base   4.6.0-2 → 4.6.0-7
 libstdc++6     4.6.0-2 → 4.6.0-7
 libgcc1        1:4.6.0-2 → 1:4.6.0-7
 tasksel        2.89 → 3.01
 tasksel-data   2.89 → 3.01

dpkg.log attached.

Attachment: dpkg.log.xz
Description: Binary data

Reply via email to