Your message dated Tue, 28 Jan 2020 02:24:03 +0100
with message-id <4058bb55-fcd7-4f64-7039-210cff5df...@debian.org>
and subject line Re: libpam-systemd: Please relax Depends: systemd-sysv
has caused the Debian Bug report #935304,
regarding libpam-systemd: Please relax Depends: systemd-sysv
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
935304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpam-systemd
Version: 241-7
Severity: normal
Dear systemd maintainers,
Please would you reconsider libpam-systemd's dependency on systemd-sysv?
This dependency makes switching from libpam-systemd to libpam-elogind on desktop
systems difficult with out removing and the reinstalling many components one
libpam-elogind is installed.
systemd cannot be removed whilst it is PID 1 so sysvinit-core needs to be
installed first and the system rebooted. sysvinit-core conflicts with
systemd-sysv and libpam-systemd depends systemd-sysv. So installing
sysvinit-core forces the removal of anything depending on libpam-systemd
including the majority of many desktops.
I can imagine the original intention of the dependency was to ensure systemd was
the active init. However, even with systemd-sysv installed, it is still possible
to boot with init=/bin/sh on the kernel commandline or change the init in grub
menu. So the dependency fails to ensure systemd is PID 1.
I suggest that Recommends would be a more suitable relationship.
Thanks
Mark
--- End Message ---
--- Begin Message ---
On Wed, 21 Aug 2019 14:29:52 +0100 Mark Hindley <m...@hindley.org.uk> wrote:
> Package: libpam-systemd
> Version: 241-7
> Severity: normal
>
> Dear systemd maintainers,
>
> Please would you reconsider libpam-systemd's dependency on systemd-sysv?
> This dependency makes switching from libpam-systemd to libpam-elogind on
> desktop
> systems difficult with out removing and the reinstalling many components one
> libpam-elogind is installed.
>
> systemd cannot be removed whilst it is PID 1 so sysvinit-core needs to be
> installed first and the system rebooted. sysvinit-core conflicts with
> systemd-sysv and libpam-systemd depends systemd-sysv. So installing
> sysvinit-core forces the removal of anything depending on libpam-systemd
> including the majority of many desktops.
>
> I can imagine the original intention of the dependency was to ensure systemd
> was
> the active init. However, even with systemd-sysv installed, it is still
> possible
> to boot with init=/bin/sh on the kernel commandline or change the init in grub
> menu. So the dependency fails to ensure systemd is PID 1.
>
> I suggest that Recommends would be a more suitable relationship.
I gave this some more thought and while I can sympathize with your
situation, I think the proposed solution is the incorrect one.
libpam-systemd does require systemd to be the active PID 1. The
systemd-sysv dependency is the closest guarantee we have that ensures this.
Does it guarantee this is the case a 100%, maybe not, but it's pretty
close. Sure, you can modify your kernel command line to boot with
/bin/sh, but I'm sure a user who does this, doesn't expect a full
runnign system in that case. My concern is, that I want to ensure that a
user that installs a typical Debian system will end up with a coherent
set of packages. Unfortunately, Recommends do not guarantee that.
Thanks for understanding.
Michael
signature.asc
Description: OpenPGP digital signature
--- End Message ---
