Control: reassign -1 apt [ Please see the bug archive for more context. ]
Hi! On Wed, 2017-04-05 at 22:01:17 +0200, Andreas Beckmann wrote: > On 2017-04-02 01:37, Guillem Jover wrote: > > 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. > > OK, let's try that in the chroot after the failure occurred: > > # # just verify that the problem is still there > # dpkg --configure cracklib-runtime > 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: error processing package cracklib-runtime (--configure): > dependency problems - leaving triggers unprocessed > Errors were encountered while processing: > cracklib-runtime > > # dpkg --configure cracklib-runtime libcrack2 > Setting up libcrack2:i386 (2.9.2-3+b1) ... > Processing triggers for cracklib-runtime (2.9.2-1) ... > Processing triggers for libc-bin (2.24-9) ... > > # dpkg --configure --pending > Setting up perl-modules-5.24 (5.24.1-2) ... > Setting up libgdbm3:i386 (1.8.3-14) ... > Setting up libperl5.24:i386 (5.24.1-2) ... > Setting up bash (4.4-4+b1) ... > [...] > > > So the fault is in apt ... and that's jessie's version of apt that is > running the upgrade :-( > > If I start the upgrade with upgrading only apt (and its dependencies) > and thereafter running the dist-upgrade (with squeeze's version of apt), > I cannot reproduce the bug. Thanks for verifying! Reassigned now to apt. Regards, Guillem
