Bug#746578: libpam-systemd to flip dependencies - proposal
Ian Jackson <ijackson@chiark.greenend.org.uk> writes:
> Rationale (Constitution 6.1(5)):
> 1. Currently libpam-systemd (which is pulled in by quite a few
> dependency chains) Depends on `systemd-sysv | systemd-shim'.
> 2. The effect of this is that installing certain leaf packages which
> depend on libpam-systemd can cause a user's init system to be
> switched to systemd, even on systems where a user has deliberately
> chosen not to use the default init system, and even when the switch
> is unnecessary.
> 3. Swappping the order of these dependencies would avoid that and has
> no harmful effect.
> Decision (Constitution 6.1(4)):
> 4. We therefore overrule the decision of the maintainer of
> libpam-systemd binary package. The Depends entry
> systemd-sysv | systemd-shim (>= 8-2)
> should be replaced by
> systemd-shim (>= 8-2) | systemd-sysv
> Release (Constitution 6.1(5)):
> 5. We request that the Release Team allow this change to into jessie.
> (This request should be conveyed to the Release Team, after the
> change is in unstable, by filing an unblock request in the usual
> way.)
This looks fine to me.
So, this is also the last call for anyone to explain what harmful effect
this could have if they think it would have a harmful effect. My
understanding is that all of the possible harmful effects have been fixed
by various other changes.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: