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

Adam Borowski kilobyte at angband.pl
Tue Aug 13 21:16:01 BST 2019

On Tue, Aug 13, 2019 at 07:58:09PM +0100, Mark Hindley wrote:
> On Tue, Aug 13, 2019 at 04:46:32PM +0200, Thorsten Glaser wrote:
> > On Sun, 11 Aug 2019, Simon McVittie wrote:
> > > Found while preparing a test VM to test #923240. Please raise this to
> > > RC severity if you think it is justified - I don't want to create the
> > 
> > I don’t think it’s RC in any of the involved packages (elogind,
> > systemd (shock!), apt) because it’s really a whole-system / package
> > management issue.
> Yes, that is my conclusion after 2 days of trying different things. Certainly
> systemd's prerm failure is pretty brutal. But this happens before any of the
> src:elogind preinsts run, so I can't see a way around it.

The prerm also makes systemd non-removable without uninstalling most packages,
rebooting, then installing anew.  Requiring such a reinstall is pretty much
RC in by book.

I've reported this before as #930105 but this got insta-closed+downgraded by
mbiebl.  On the other hand, mbiebl routinely does this (or reports RC bugs
on perfectly working packages without naming a reason), thus the closure
might have not been related to merits or lack thereof.

[I'm in Sao Paulo airport, after a day of travel and about to embark again,
thus I can't investigate yet.  Not before going home then around a week of

⣾⠁⢠⠒⠀⣿⡁ Debian is one big family.  Including that weird uncle
⢿⡄⠘⠷⠚⠋⠀ and ultra-religious in-laws.

More information about the Debian-init-diversity mailing list