On Sep 06, Otto Kekäläinen <o...@debian.org> wrote:

> Something in the upgrade logic to adopt the new pacakge is lacking
> when upgrading libc6 as the system ends in a situation where
> libcrypt.so.1 is removed before the replacement from a new package is
> installed.
Yes, I think that this happens because perl-base Pre-Depends on 
libcrypt1, but since perl-base is not being upgraded in your example 
then there is nothing which will pull libcrypt1 in.
The interesting questions here is why this does not happen when 
upgrading from Debian 10 to 11, or at least not frequently enough to be 
noticed?
If the fix (Breaks perl-base in libc6?) does not have too many 
collateral effects then it may be worth implementing it anyway even if 
9 -> 12 upgrades are not officially supported.

-- 
ciao,
Marco

Attachment: signature.asc
Description: PGP signature

Reply via email to