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.
I put old systemd stuff on hold until this is sorted out. Did not notice
any problem with that.
> 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.
This should be a temporary problem until cgmanager makes its way into sid
and systemd-shim can start uting it.
There were two maintainers trying to package cgmanager independently and
have it into NEW. That was the reason for rejection. Both maintainers are
currently working together to get the cgmanager package ready, even if
merging changes from both sides means some days of delay (See #754910).