On Tue, 2013-10-29 at 00:51 -0700, Steve Langasek wrote: > > (Also, do remember that any decisive outcome other than “support > > multiple ones including systemd” and “systemd-only” will need to > > lead to the removal of GNOME from Debian. > > Absolutely not true. As Tollef mentions in his follow-up, one of the > options is to fork logind and maintain it. > > This is not an improbable outcome. Logind is a good interface, and there's > a lot of value in continuing to use it, regardless of what init system we > choose. If Debian chooses to ship upstart as the default, I will almost > certainly be inteested in making sure that logind continues to be > well-supported on top of upstart, in both Debian and Ubuntu. The work to do > this on Ubuntu has so far been straightforward; while there are some > technical hurdles in the future for making logind continue to work on > non-systemd systems, these are known issues and not at all insurmountable.
Some more systemd-login0 dependencies: apt-cache rdepends libsystemd-login0 weston gnome-disk-utility build-rdeps libsystemd-login-dev (not only [linux-any]) gnome-disk-utility gnome-disk-utility also depends on libudisks2-dev which depends on udev, which is linux-any/built from systemd?, so this one might be impossible outside linux anyway. weston is Architecture: linux-any but isn't it supposed to run on other architectures in the future? Looks like systemd is creping in everywhere. See also the problems with gdm3 not starting #724731, systemd-login0 and libpam-systemd. That bug hit me too, on a brand new box as reported earlier. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1383087069.11925.29.ca...@g3620.my.own.domain