[looping in bluca as well]On Thu, 24 Jul 2025 02:43:27 +0200 Chris Hofstaedtler <z...@debian.org> wrote:
On Sun, Jul 13, 2025 at 10:29:25AM +0200, Helmut Grohne wrote: > Hi Chris,> > On Sat, Jul 12, 2025 at 12:36:20AM +0200, Chris Hofstaedtler wrote:> > I was somewhat hoping this is caused by the existing upgrade issue which > > Helmut is working on AFAIU. Was it proven that this is not the same problem?> > I believe this is independent and I merely caught it as I was carefully > reading test results for your other issue. This particular one is solely > caused by libssl3 having done a t64 transition when it was not > appropriate to do so. I do not expect my proposed change to glibc to > improve the situation regarding systemctl.Is this problem still happening? If so, are there any ideas on what to do about it?
Not sure if it's relevant, but I post it here for completeness sake:To make systemctl more robust during dist-upgrades, in the past we built systemd with `-Dlink-systemctl-shared=false`, so systemctl has a minimal set of library dependencies and then we added all those library dependencies to Pre-Depends via
https://salsa.debian.org/systemd-team/systemd/-/blob/debian/master/debian/rules?ref_type=heads#L302This was under the assumption that systemctl is quasi-essential and can be triggered at arbitrary times during a dist-upgrades.
Luca changed that (recently) in https://salsa.debian.org/systemd-team/systemd/-/commit/8ca2b266789bff0b1af348100e72da7245864174I.e. systemctl now links against libsystemd-shared which in turn has a couple of side-effects
a/ libsystemd-shared is not an so-versioned package, i.e. different versions can not be co-installed. So there is a time window where systemctl is in a non-functional state, e.g. when you have an old systemd + new libsystemd-shared or a new systemd + old libsystemd-shared unpacked
This could be addressed by making libsystemd-shared so-versioned, i.e. naming it libsystemd-shared-$VER or going back to linking systemctl statically against libsystemd-shared.
b/ If Luca want's to continue to use `-Dlink-systemctl-shared=true`, maybe it would make sense to treat all those library dependencies of libsystemd-shared as Pre-Depends.
We are rather late in the trixie release cycle, so maybe the safest approach is to revert 8ca2b266789bff0b1af348100e72da7245864174 for trixie and re-apply it early during the forky release?
Michael
OpenPGP_signature.asc
Description: OpenPGP digital signature
