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

Thorsten Glaser t.glaser at tarent.de
Tue Aug 13 21:56:01 BST 2019

On Tue, 13 Aug 2019, Adam Borowski wrote:

> > 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

Not exactly what you wrote, but I see it now (M-A same vs foreign,
even though libpam-elogind is no library package and contains a
conffile additioinally).

There is no libpam-systemd in this equation.

So then, rename elogind to elogind-daemon instead of merging it,
and let libpam-elogind depend on elogind-daemon. The rest still
stands (it is important that installing a package called simply
“elogind” is the final step after a potential reboot, for being
able to tell people to “just install elogind”).

This would solve two of my confusions.

tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg


Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.


More information about the Debian-init-diversity mailing list