Hi! [ Sorry for taking so much time to dig into this. Reproducing, checking and diagnosing trigger issues imply usually spending significant amounts of time on it, which I didn't have back then, and it's a bit of a drag to be the "support channel" for trigger issues too. :)
Anyway, thanks go to Niels, who by looking into this, prompted me to do the same. ;) ] On Wed, 2017-02-08 at 11:42:29 +0100, Andreas Beckmann wrote: > Package: dpkg > Version: 1.18.18 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > Control: affects -1 + libcrypt-cracklib-perl > I just noticed this trigger related problem during a piuparts upgrade > test of libcrypt-cracklib-perl from jessie to stretch. I can reproduce > it on both amd64 and i386, but it requires --install-recommends to show > up. If you need more debug info, I can now easily rerun the failed tests > and enter the chroot after the failure to collect more info. > > >From the attached log (scroll to the bottom...): > > [...] > Preparing to unpack .../archives/bash_4.4-4_i386.deb ... > Unpacking bash (4.4-4) over (4.3-11+deb8u1) ... > dpkg: dependency problems prevent processing triggers for cracklib-runtime: > cracklib-runtime depends on libcrack2 (>= 2.9.2-1); however: > Package libcrack2:i386 is not configured yet. […] > dpkg: too many errors, stopping > Errors were encountered while processing: > cracklib-runtime […] > cracklib-runtime > Processing wE: Sub-process /usr/bin/dpkg returned an error code (1) I think this is an issue with apt explicitly asking dpkg to configure only cracklib-runtime when its dependencies are not satisfied because they are awaiting on trigger processing, and apt is not asking for those other packages to be configured too. So dpkg cannot fulfill the request. I think a simple reproducer on a clean chroot, is to: $ cd /var/cache/apt/archives $ apt-get install --install-recommends libcrypt-cracklib-perl $ dpkg --unpack libcrack2_*.deb $ dpkg --install wamerican_*.deb $ dpkg --configure cracklib-runtime My expectation is that after the reported state is found on piuparts, running: $ dpkg --configure --pending or even something like: $ dpkg --configure cracklib-runtime libcrack2 would let dpkg configure that package correctly w/o complaining about the unsatisfiable dependency. Andreas, is that indeed the case? If it is then this needs to be reassigned to apt. Thanks, Guillem
