Control: severity -1 minor Control: retitle -1 dpkg: possible repeated messages on trigger processing error
Hi! On Sat, 2014-11-29 at 12:14:04 +0100, Eduard Bloch wrote: > Package: dpkg > Version: 1.17.22 > Severity: grave > today I tried to dist-upgrade my system (sid) starting from a package > state of a couple of weeks ago. First apt reported a failed dpkg right > in the middle of the upgrade process without displaying any visible > error messages. That would be apt bug #765687. > Now when I run "apt-get -f install" or attempt to > install some missing package explicitly, it ends up in a loop where dpkg > runs maintainer scripts on dbus without end. Here is dpkg.log and some > console output: And this seems to be related to apt bug #771428. I assume that if you just run «dpkg --configure --pending» the problem will get sorted out. If this cannot be fixed in apt, because it requires it to upgrade itself first, then I guess making dbus switch to a noawaiting trigger directive should work, and I don't think it needs the awaiting variant so that would be a correct fix anyway. > dpkg: dependency problems prevent processing triggers for dbus: > dbus depends on libexpat1 (>= 2.0.1); however: > Package libexpat1:amd64 is not configured yet. >· > dpkg: error processing package dbus (--configure): > dependency problems - leaving triggers unprocessed […] > dpkg: too many errors, stopping > Errors were encountered while processing: > dbus […] > dbus > Processing was halted because there were too many errors. > E: Sub-process /usr/bin/dpkg returned an error code (1) In any case the above duplicated error messages, is a known (at least to me) minor issue that is caused by dpkg detecting the error for the triggers case, but not making it known to the queue processor to avoid trying to go on the same path and just quiting outright. Which in the end gets stopped by the too many errors check dpkg has. I left it as is, because a fix was going to be too intrusive at this point of the freeze, and as this is always a problem in the packages (a trigger cycle) or in the frontend, and the possible dpkg processing loop always gets caught, it ends up being mostly a cosmetic issue. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
