Bug#854554: dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch

On Thu, 27 Apr 2017 18:10:17 +0200 Andreas Beckmann wrote: > Followup-For: Bug #854554 > Control: found -1 2.9.2-4 > Control: affects -1 + libcrypt-cracklib-perl > > Hi, > Hi Jan, Thanks for fixing the original part of this bug. Andreas noticed a deficiency in the suggested

Bug#854554: dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch

Followup-For: Bug #854554 Control: found -1 2.9.2-4 Control: affects -1 + libcrypt-cracklib-perl Hi, this problem has been solved completely, yet, since nothing prevents the old cracklib-runtime from being triggered during the upgrade. (Could be a problem in jessie's apt and therefore needs to

Bug#854554: dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch

Control: reassign -1 cracklib-runtime Control: forcemerge -1 cracklib2 Control: severity 854554 grave David Kalnischkies: > Control: reassign -1 libcrypt-cracklib-perl 1.7-2 > # beware, this is an RC bug! > > [CC'ed cracklib2 & perl maintainers as it seems to be some "funny" > interaction

Bug#854554: dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch

Control: reassign -1 libcrypt-cracklib-perl 1.7-2 # beware, this is an RC bug! [CC'ed cracklib2 & perl maintainers as it seems to be some "funny" interaction between packages in their responsibility space.] On Sat, Apr 08, 2017 at 04:50:15AM +0200, Guillem Jover wrote: > [ Please see the bug

Bug#854554: dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch

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

Bug#854554: dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch

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

Bug#854554: dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch

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,

Bug#854554: dpkg: trigger problem with cracklib-runtime while upgrading libcrypt-cracklib-perl from jessie to stretch

Package: dpkg Version: 1.18.18 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + libcrypt-cracklib-perl Hi, 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