Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

Cristian Ionescu-Idbohrn cristian.ionescu-idbohrn at axis.com
Sun Sep 29 09:28:01 BST 2019


On Sat, 28 Sep 2019, Thorsten Glaser wrote:
> On Sat, 28 Sep 2019, Cristian Ionescu-Idbohrn wrote:
> 
> > 1. install sysvinit-core; that removes systemd-sysv but nothing else 
> >    systemd related
> 
> > Souldn't that work?
> 
> It would, if but for libpam-systemd having a (somewhat questionable
> but understandable) dependency on systemd-sysv. This is basically
> what spawned this thread.
> 
> So we'll not be going there.

Right.  I see now what happens on my systems.  I have an older version 
of systemd packages installed:

,----
| Version: 238-5
`----

which depends on:

,----
| systemd-shim (>= 10-3~) | systemd-sysv
`----

as I stopped systemd related package updates:

,---- [ /etc/apt/preferences.d/no-systemd ]
| Package: systemd systemd-sysv systemd-sysv:i386 libsystemd0 libpam-systemd 
| Pin: release o=Debian
| Pin-Priority: -1
`----

at the point when systemd-shim was removed.


Cheers,

-- 
Cristian




More information about the Debian-init-diversity mailing list