Re: Bug#1109119: upgrade-reports: systemctl occasionally fails loading libcrypto.so

[Chris Hofstaedtler <zeha@debian.org>]

* Richard Lewis <richard.lewis.debian@googlemail.com> [250712 00:04]:
> Helmut Grohne <helmut@subdivi.de> writes:
>
> > while working on a bookworm -> trixie upgrade failure, I noticed a strange line
> > showing up.
> >
> > | Preparing to unpack .../openssh-server_1%3a10.0p1-5_amd64.deb ...
> > | systemctl: error while loading shared libraries: libcrypto.so.3: cannot open shared object file: No such file or directory
>
> > deb-systemd-invoke is part of init-system-helpers and therefore
> > essential. It calls out to systemctl, which is not essential but for all
> > practical matters we really should be treating it as if it was and
> > maintainer scripts expect it to work at all times.
>
> > In practice, this means that systemctl cannot be expected to work in
> > maintainer scripts.
>
> forgive the stupid question: does this mean there is a wider risk that
> this might affect other packages?

Yes.

> "systemctl is de-facto essential but not marked as such" sounds quite dangerous

Not really. You can consider it pseudo-essential on a lot of 
systems, but certainly not all.

It would certainly suck if the common case was broken. The package 
containing systemctl not being marked Essential: yes is however, 
correct.

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?

Chris