Control: forcemerge 766242 -1 On Fri, 2014-10-24 at 03:32:49 +0200, Christoph Anton Mitterer wrote: > On Fri, 2014-10-24 at 03:23 +0200, Christoph Anton Mitterer wrote: > > So that's kinda worrisome... how to get out of this when one cannot > > upgrade to a newer version of dpkg?
This was already filed, and fixed in 1.17.20… > I could dpkg --configure debian-security-support, which already solved > the triggers-aWaited for many other packagees,... and then another dpkg > --configure -a configured all the unconfigured leftovers. … but debian-security-support is causing a trigger cycle, that dpkg does not detect anymore, and will make it assert when it runs out of steps to do and the queue is still full. That will be fixed in 1.17.21. > Guillem,... any ideas whether/how these kills (or pressing Ctrl-C) > affects the dpkg status DB and other metadata? > Should I be worried and look whether I need to import backups? At least > at a first glance, everything looks normal again, though, in aptitude. Nope, none of this should cause any issue to the dpkg database. dpkg takes care of doing correct atomic updates to it, and using an update log. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
