Your message dated Fri, 11 Sep 2015 16:14:34 +0100 with message-id <capq4b8mgkaq4wmuny+gzynh2vqtq0qd4ijhvslupokgrv6g...@mail.gmail.com> and subject line Re: [Aptitude-devel] Bug#769222: Bug#769222: Bug#769222: aptitude: Frequent pending actions left has caused the Debian Bug report #769222, regarding aptitude: Can't configure packages from trigger/wait states 'T' and 'W' (frequent pending actions left; says, it would configure packages but doesn't) to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 769222: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769222 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: aptitude Version: 0.6.11-1+b1 Severity: normal On three different PCs (Debian unstable, i386, 32 bit) i'm frequently encountering a problem, where aptitude (curses interface), without any error to the user, leaves some package in an incomplete state. I usually follow these steps: - run aptitude from the curses interface. - update the package list. - install all the available upgrade. This process always goes fine, but if after run deborphan it says: ----------- deborphan: The status file is in an improper state. One or more packages are marked as half-installed, half-configured, unpacked, triggers-awaited or triggers-pending. Exiting. ----------- And it is right, because if i return to aptitude, and press "g", i find a list of some partially installed package. For example, today in the machine from where i'm reporting this bug, i can see the attached situation. If i run "dpkg -C" it says: ----------- The following packages are awaiting processing of triggers that they have activated in other packages. This processing can be requested using dselect or dpkg --configure --pending (or dpkg --triggers-only): libwmf0.2-7:amd64 Windows metafile conversion library The following packages have been triggered, but the trigger processing has not yet been done. Trigger processing can be requested using dselect or dpkg --configure --pending (or dpkg --triggers-only): libgdk-pixbuf2.0-0:amd64 GDK Pixbuf library ----------- Aptitude seems not able to correct this situation: if you press "g", then "g" to repeat the install process, nothing happens. Using the aptitude curses interface i'm usually able to clean this situation reinstalling ("L") the packages listes as partially installed. But i prefer to resolve with this command: dpkg --configure -a I'm not sure, but i believe that this problem appeared after one of the recent dpkg upgrade. Cesare. -- Package-specific info: Terminal: xterm $DISPLAY is set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.6.11 compiled at Nov 8 2014 13:34:39 Compiler: g++ 4.9.1 Compiled against: apt version 4.12.0 NCurses version 5.9 libsigc++ version: 2.4.0 Gtk+ support disabled. Qt support disabled. Current library versions: NCurses version: ncurses 5.9.20140913 cwidget version: 0.5.17 Apt version: 4.12.0 aptitude linkage: linux-vdso.so.1 (0x00007fff8bb9b000) libapt-pkg.so.4.12 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 (0x00007f81267fa000) libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 (0x00007f81265c4000) libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x00007f8126399000) libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 (0x00007f8126193000) libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 (0x00007f8125e7d000) libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x00007f8125bb4000) libboost_iostreams.so.1.55.0 => /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.55.0 (0x00007f812599c000) libxapian.so.22 => /usr/lib/libxapian.so.22 (0x00007f812558b000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f812536d000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f8125062000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f8124d61000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f8124b4a000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f81247a1000) libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007f812459e000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f8124399000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f812417e000) libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x00007f8123f6e000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f8123d4a000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f8123b42000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007f812393c000) /lib64/ld-linux-x86-64.so.2 (0x00007f81271cf000) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages aptitude depends on: ii aptitude-common 0.6.11-1 ii libapt-pkg4.12 1.0.9.3 ii libboost-iostreams1.55.0 1.55.0+dfsg-3 ii libc6 2.19-13 ii libcwidget3 0.5.17-2 ii libgcc1 1:4.9.2-1 ii libncursesw5 5.9+20140913-1 ii libsigc++-2.0-0c2a 2.4.0-1 ii libsqlite3-0 3.8.7.1-1 ii libstdc++6 4.9.2-1 ii libtinfo5 5.9+20140913-1 ii libxapian22 1.2.19-1 Versions of packages aptitude recommends: pn aptitude-doc-en | aptitude-doc <none> ii libparse-debianchangelog-perl 1.2.0-1.1 ii sensible-utils 0.0.9 Versions of packages aptitude suggests: pn apt-xapian-index <none> pn debtags <none> ii tasksel 3.29 -- no debconf information
--- End Message ---
--- Begin Message ---2015-09-11 10:25 GMT+01:00 David Kalnischkies <[email protected]>: > On Fri, Sep 11, 2015 at 01:06:24AM +0100, Manuel A. Fernandez Montecelo wrote: >> >I haven't really decided (mostly thanks to time issues) yet how to tackle >> >this giant ball of pain and on top of that how to sell it to the Release >> >Team if I would find a fix from the apt side. As said in the mentioned >> >bugreport, that wouldn't help in any way with wheezy-upgrades though. > > [The bugreport was 769609 and the fix which landed in jessie with > Release team approval was a2a75ff4516f7609f4c55b42270abb8d08943c60.] > > >> In the dpkg commit fixing #766758, it says: >> >> This is a mostly conformant workaround for frontends like apt that do >> not correctly call «dpkg --configure -a» or «dpkg --triggers-only -a» >> after their normal runs, and leave packages in triggers-pending and >> triggers-awaited states. > > apt/jessie does call "dpkg --configure -a" by default after performing > its other dpkg callings. The workaround was needed as apt/wheezy is used > in the wheezy→jessie upgrade, while at some point in this upgrade > dpkg/jessie will be used; so dpkg has to behave as apt/wheezy expects it > to work. > > [The "bleed through" of internal details like triggers is why we would > prefer that dpkg would deal with ordering all by itself as talked about > in the DebConf meeting] I see, I didn't realise at the time when you were discussing that. >> I am not sure if the front-ends are suppossed to be modified to call >> dpkg correctly because this "conformant workaround" will be removed, or >> what's the situation. Can you please clarify, if you know the reply >> right away? If you have to dig no problem, I will do it. > > I am pretty sure the workaround will be removed at some point, so if > aptitude calls dpkg itself in any way, it should call --configure -a at > the end of these actions – "--configure pkg" might be the most likely > situation to activate a trigger but any file placement or maintainer > script can call one. > > I don't know if aptitude actually calls dpkg on its own, but some > reports I had read suggested as much even through I wouldn't expect it… > So I left this bug here for someone to check aptitude – feel free to > close if there is no such issue. I've been reviewing the calls and, unless I am missing somethig, there are no calls of that kind, there are only other calls to dpkg for different purposes. So I think that it is safe to close the bug now. Thanks a lot for the input! -- Manuel A. Fernandez Montecelo <[email protected]>
--- End Message ---
_______________________________________________ Aptitude-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
