Le 26/05/2024 à 21:58, Sebastian Andrzej Siewior a écrit :
It seems to me that having both :i386 and :amd64 libraries increases the
risk of failure, because of the many "apt" steps that can take place between
the removal of old :amd64 (that may happen close to the treatment of the
:i386 version, like here for libssl3) and install of t64:amd64. On the
contrary, when only :amd64 is present, it seems that the replacement install
closely follows the removal.
how did you have two versions? I couldn't install :amd64 and :i386 of
that package. I tried several bookworm -> testing upgrade but in
bookworm I could install either :i386 or :amd64 version of postgres.
Installing the other version removed the former…
I performed a few upgrades and all succeeded. Anyway to reproduce what
you did?
I have only version :amd64 of postgresql.
(As a reminder, it was systemctl:amd64 that failed during upgrade of
postgresql-16, because libssl3:amd64 had been removed "at the same time"
than libssl3:i386, and only libssl3t64:i386 had been installed then —
libssl3t64:amd64 was likely planned to get installed later.)
It was other packages, in the past, that have required :i386 libraries.
I don’t remember which packages now.
For example, I have an old skype:i386 installed (version: 4.3.0.37-1),
that depended on libssl1.0.0. Maybe that caused libssl3:i386 to become
installed through some upgrade path. (Or maybe libssl3 was a dependency
from another :i386 package.)
To reproduce, you would likely have to have some :i386 package
installed, that depended on libssl3:i386. (Or maybe just libssl3:i386
would be enough?)
Jean-Guilhem
