Hi! On Fri, 2014-10-24 at 02:23:22 +0200, Guillem Jover wrote: > Control: severity -1 serious > > On Fri, 2014-10-24 at 01:40:41 +0200, Axel Beckert wrote: > > Package: dpkg > > Version: 1.17.20 > > Severity: grave > > Justification: breaks whole package management > > Not for everyone, so serious is about right (not much of a difference > but still). :( > > > after the upgrade to 1.17.20, dpkg crashes reproducibly with the > > following error message: > > > > dpkg: ../../src/packages.c:226: process_queue: Assertion `dependtry <= 4' > > failed. > > Aborted (core dumped) > > > > aptitude refuses to make further package changes and says I should run > > "dpkg --configure -a". But if I try that, it crashes again: > > > > # dpkg --configure -a > > dpkg: ../../src/packages.c:226: process_queue: Assertion `dependtry <= 4' > > failed. > > Aborted (core dumped) > > Axel has sent me additional (possibly sensitive/personal) status files > off-bts, and I'm tracking it down right now.
Which I tracked and I've fixed locally. This is actually due to an undetected trigger cycle, caused by debian-security-support (#762031), which makes a metric ton of packages await triggers. I'm thinking how to best handle all this mess, because last time I analyzed the triggers there were way too many that are not using noawait, but I'm not sure how many create cycles. I think I'll just upload tomorrow morning the fix to get systems unstuck, also commit a patch I have around to add explicit --await, interest-await and activate-await, so that the implicit one can be warned on during the jessie+1 cycle and later deprecated; and maybe disable the trigger dependency checks for jessie, depending on the amount of cycles found and how and if they get fixed. :/ Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
