Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing
Cristian Ionescu-Idbohrn
cristian.ionescu-idbohrn at axis.com
Sat Sep 21 17:51:16 BST 2019
On Sat, 21 Sep 2019, Mark Hindley wrote:
> On Sat, Sep 21, 2019 at 04:35:39PM +0200, Cristian Ionescu-Idbohrn wrote:
> > I'm interested in this, but my systems (unstable and testing) are
> > in a slightly different state. Let's take unstable, for example:
>
> Thanks for this. However, I really don't see it as relating to
> Simon's original report.
>
> Would you, please, start a new bug for this unless you really think
> it is the same issue (apt being broken by continuing to uninstall
> libsystemd0 after systemd prerm fails) and I will be happy to help.
I really don't know what to think, but I do really feel this is not
related to the systemd installed version. Any current systemd version
should be removed without affecting the state. Am I wrong?
Cheers,
--
Cristian
More information about the Debian-init-diversity
mailing list