Raphael Hertzog writes ("About triggers"): > On this topic, I'd like to get your opinion on #143307. It looks like > that the the trigger handling leads to more "cycles" in dependencies > since some packages must be triggered before being configured.
I think this explanation is a red herring. > I thought that we had two different states "trigger pending" > and "trigger awaited" precisely to be able to consider one state as > as configured while the other would not. But I've never seen that > difference in those scenarios and I'm worried by the increased > number of such errors... apt-get ask to run dpkg --configure -a > and dpkg --configure -a fails badly. Yes. > Can you investigate a bit and give me your opinion in the corresponding > bug log? If I have a /var/lib/dpkg/status file (and corresponding /var/lib/dpkg/updates/*, if applicable) which makes the bug reproduceable then I can fix the bug. Ian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]