Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

Mark Hindley mark at hindley.org.uk
Tue Aug 27 17:46:32 BST 2019

Control: block -1 935910

On Thu, Aug 15, 2019 at 08:42:35PM +0100, Mark Hindley wrote:
> > > Unsure if that’s apt or dpkg. Plus, the failing prerm is in systemd,
> > > not in libsystemd0.
> > 
> > I think this is probably dpkg, but it's dpkg being told what to do by
> > apt, so it could be either one causing this. I would have hoped that if
> > systemd.prerm fails, that's a fairly heavy hint that not only is it not
> > OK to remove systemd at this time, it's also not OK to remove systemd's
> > dependencies.


I think I have finally got to the bottom of this. As you suspected it is apt's
invocation of dpkg. See #935910.


More information about the Debian-init-diversity mailing list