Bug#935304: libpam-systemd: Please relax Depends: systemd-sysv (was: Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful) (fwd)

[Cristian Ionescu-Idbohrn]

Bummer...  Sorry, was #935304 it was aimed for.

---------- Forwarded message ----------
Date: Sun, 29 Sep 2019 11:00:10 +0200 (CEST)
From: Cristian Ionescu-Idbohrn <cristian.ionescu-idbohrn at axis.com>
To: 940034 at bugs.debian.org

On Sun, 29 Sep 2019, Mark Hindley wrote:
> On Sat, Sep 28, 2019 at 11:41:56AM +0200, 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.
> 
> Thorsten is quite right.
> 
> There is already a separate bug concerning the libpam-systemd 
> systemd-sysv dependency. See https://bugs.debian.org/935304. That 
> would be a more appropriate place for you to add any comments you 
> may have regarding this aspect of the behaviour you have observed.

Following Mark's advice, here are my findings:

On Sun, 29 Sep 2019, Cristian Ionescu-Idbohrn wrote:
> 
> 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.

Does it mean that, in my case, the transition to elogind would be 
easier?


Cheers,

-- 
Cristian