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:49:47 BST 2019

On Tue, Aug 13, 2019 at 10:43:30PM +0200, Thorsten Glaser wrote:
> On Tue, 13 Aug 2019, Adam Borowski wrote:
> > 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
> Hm ☹ but I just had this crazy idea:
> 1. Merge elogind into libpam-elogind (not the other way round),
>    as elogind without libpam-elogind is apparently (see the
>    other thread) not useful in any way.

I don't think it's reasonable to have the daemon in a library package.

There's also multiarch to think about:
foo:pdp11 Depends libpam-systemd:pdp11

> If this is not suitable I’m blaming the beer I’ve had with supper.

[The queue to board is almost over...]

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

More information about the Debian-init-diversity mailing list