Should libpam-elogind Provide libpam-systemd ?

Martin Steigerwald martin at
Tue Nov 6 16:04:07 GMT 2018

Mark Hindley - 06.11.18, 14:47:
> > Clear recommendations from the thread:
> > 
> > Don't provide libpam-systemd.
> From Devuan's perspactive that is a shame. Devuan uses libpam-elogind
> providing libpam-systemd as a way of providing the necessary
> functionality without modifying a host of Debian packages.

If these packages can be adapted in Debian, Devuan still would not need 
to modify those.

Main thing is that packages depend on libpam-systemd for two different 
reasons as Ian already wrote. Quoted from Felipe Sateler, Pulseaudio 
maintainer in Debian:

Felipe Sateler - 06.11.18, 14:41:
> I agree providing libpam-systemd is wrong. As noted elsewhere on this
> thread, libpam-systemd provides two related services:
> 1. systemd-logind integration
> 2. systemd --user integration
> Therefore I think we need two virtual packages, to signal the
> dependency on each service. That way, libpam-elogind can provide the
> first one but not the latter. Packages requiring (or wanting) can
> Depend (or Recommend) the latter. As usual for multiple providing
> packages, there should be a default-foo alternative listed first.
> I'll leave the hard problem of naming the packages to others 

<CAAfdZj9Ctfah9jxniqs5pYsd2+EZYX9F903n2HMDnexOkX1O2Q at>

Of course I suggest to continue to discuss this on debian-devel by 
replying to the mail there. Otherwise there would be the same discussion 
on two mailing lists. Ian already did a marvelous job with summarizing 
one-way. Let's not confuse him totally :)


More information about the Debian-init-diversity mailing list