[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: systemd now appears to be only possible init system in testing

On Tue, Jul 22, 2014 at 10:54:55PM +0100, Julian Gilbey wrote:
> I just tried updating testing on my system.  I currently use
> sysvinit-core (reasons below), but aptitude is telling me that I
> should remove this in favour of systemd-sysv.  Hmm, why is that?
> Well, because the new version of libpam-systemd, 208-6, now depends on
> systemd-sysv rather than systemd-sysv | systemd-shim.  OK, so I'll
> remove libpam-systemd.  Ooops - that looks pretty disastrous, as so
> much depends on it, so that's not an option: gdm3, gnome-bluetooth,
> network-manager, policykit-1, udisks2.

> So I would presume that for many or most Debian systems, systemd is
> now required, and no other /sbin/init providers will work.  I'm
> unclear whether this was a deliberate policy decision or an unintended
> consequence of various package requirements.

See bug #752939, which is currently blocked on cgmanager, which was in the
NEW queue but for some reason seems to have been rejected rather than

Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek@ubuntu.com                                     vorlon@debian.org

Attachment: signature.asc
Description: Digital signature

Reply to: