Bug#645540: "Essential" package conflict between sysvinit and systemd-sysv

This is an OpenPGP/MIME signed message (RFC 2440 and 3156) Instead of trying to make system(-sysv) Essential, I'm wondering if we can't just drop the Essential flag from sysvinit. At least the special semantic property of an Essential package - ...

Message posted on the February 6th, 2012 - 12:50 PM ET

systemd-sysvinit can't be essential since that'd force it onto all systems. I suppose, then, that implies that a "virtual package" - "init", for instance - would have to be marked "Essential", and that both sysvinit ...

Message posted on the October 22nd, 2011 - 10:50 AM ET

Bug#645540: "Essential" package conflict between sysvinit and systemd-sysv

Package: sysvinit Version: 2.88dsf-13.12 I'd recommend just booting with init=/bin/systemd, tbh. It's what I (as the systemd maintainer) do on my own systems. Well, that seems ironic, in that I would have expected the sytemd maintainer himself ...

Message posted on the October 21st, 2011 - 11:00 PM ET

Bug#645540: "Essential" package conflict between sysvinit and systemd-sysv

Package: sysvinit Version: 2.88dsf-13.12 _Please_ resolve the "Essential" package conflict between sysvinit and systemd-sysv. For those of us running testing/Wheezy or unstable/Sid with systemd, _every_single_time_ there is an upgrade - ...

Message posted on the October 16th, 2011 - 4:40 PM ET

Comments on introducing a new Essential package: base-init?

This is regarding Bug #645540 ("Essential" package conflict between sysvinit and systemd-sysv). sysvinit is currently Essential. In order to permit the replacement of sysvinit with an alternative init system, I'd like to propose the ...

Message posted on the February 8th, 2012 - 3:10 PM ET

bug 645540