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

Simon McVittie smcv at debian.org
Thu Aug 15 19:57:42 BST 2019

On Thu, 15 Aug 2019 at 18:34:39 +0200, Thorsten Glaser wrote:
> On Thu, 15 Aug 2019, Mark Hindley wrote:
> > Can you point me to any official documentation that says packages
> > should not depend on systemd-sysv?
> No, but why should they?

For documentation value, if nothing else: it's a way to say "this package
genuinely does need systemd as pid 1, and won't work without it".

> It does not guarantee that systemd is the currently-running init,
> nor that this will be so at the next boot.

No, and it's imperfect for those reasons; but for this not to be the
case, you have to override the init system in ways that you will hopefully
remember that you have done.


More information about the Debian-init-diversity mailing list