On 2014-05-16 17:33 +0200, Michael Biebl wrote:
> Incidentally we also discussed dropping the Conflicts from systemd-sysv
> and only keeping the Replaces (and this is also what sysvinit-core has
> done).
Which has its own problems, since nothing stops the admin from shooting
themselves in the foot by installing sysvinit-core without upgrading
sysvinit and then removing sysvinit-core.
> I'm a bit surprised though, that a user has hit this issue, since
> sysvinit still has sysvinit-core as first alternative. This might be due
> to the switch in libpam-systemd though.
This switch makes it totally unpredictable whether you end up with
systemd-sysv or sysvinit-core + systemd-shim, indeed.
Cheers,
Sven
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
