Bug#922160: lightdm: Add elogind support
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Wed, 2019-03-06 at 19:04 +0100, Michael Biebl wrote:
> This is usually not a good idea, as apt will pick a package at random if
> none is installed yet. You should always list a real package or
> default-logind first.
I've already changed that for the next upload locally to:
libpam-systemd [linux-any] | logind [linux-any]
but I'm happy to change to something else if there's some kind of consensus.
> That said, I think, Ansgar makes a good point here.
> Since you encode specific logind implementations in your pam config,
Note: this is not really something I want to enforce (I don't really care).
I'd be happy to change the pam configuration to something more generic. But as
already said earlier:
- - now is not the perfect time for that (let's do it for Bullseye)
- - I don't have enough clue about pam to know the potential consequences, so if
someone can give a hand here to make sure we don't end up with regressions, it
would help.
Regards,
- --
Yves-Alexis
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlyAQgQACgkQ3rYcyPpX
RFst1Qf+NNCqPnHsmsD7blB3ECsn94uwOLnYlcbjjrLREK4Dwmw3BfiEchOefrsU
pVa3eyGZH0vU+HziZ4h8dwTqe3jVGd65ngDLuek1gSPPzZusMLf9BL1CQO1NFtL/
X5gjzRNFuZp6PwrvewHpTRyM5tsCsPYy6ZwtXIApER6Fg9MZx8FTjWKlaVfIItFq
PLe4YN94jl30VK8aTpc8dLLgUyBmInYYLDdRfC2sMO3nB2semlway1LIK2N3wDsg
8we73Oxe4ojVxPEJGC+eX9zB+YzY8SFFloEarHxof3x6PUSBCa1wlVfZ7HZzyztT
mMwdd2EUjko9F0D3aoXDCQhe/HbckQ==
=Wg4Q
-----END PGP SIGNATURE-----
Reply to: