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

Niels Thykier niels at thykier.net
Sat Apr 8 08:42:00 UTC 2017


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 between packages in their responsibility space.]
> 
> [...]
> 
> 
> That said, educated guess follows:
> 
> Looks like apt acts on libcrypt-cracklib-perl early as it looks simple
> enough (after upgrading perl) as the dependency on libcrack2 is already
> satisfied at the start of the upgrade (as its a version before jessie).
> As the dependencies of libcrack2 are very lightweight (just libc6 which
> is done at that point) it might already work if you artificially require
> a stretch-version here (= guess, not tested at all).
> 
> 
> Best regards
> 
> David Kalnischkies, who is in a love-hate relationship with triggers
>

Hi,

Actually, I think a much better solution would be to solve #859307,
which would be the correct long term solution and should solve this
upgrade issue (as -noawait triggers would not be subject to this problem).

Thanks,
~Niels




More information about the pkg-perl-maintainers mailing list