Debian decides on systemd—for now

I usually try and gather and inform about whenever there are upstream changes affecting anything to do around packaging GNOME. This is done using the distributor-list mailing list, see https://mail.gnome.org/archives/distributor-list/. We also use that whenever we want feedback.

Only thing I noticed is due to talking about it, I need to explicitly tell that some things are NOT part of GNOME. E.g. ConsoleKit is on freedesktop.org. UPower, freedesktop.org. Gstreamer, freedesktop.org. I haven't done that and this results in people assuming that GNOME is forcing things. IMO we're just really aware.

End October 2013, UPower (freedesktop.org) removed the standby functionality that overlapped with systemd. I highlighted this, see https://mail.gnome.org/archives/distributor-list/2013-Oct.... It is a highlight because it is a potential issue to package GNOME. I'll inform whenever I see potential issues, irrespective of where the maintenance lies. This so people have enough time to act (prepare for the change, argue against it, whatever).

What's now happening at the moment is that projects which rely on UPower to directly rely on that standby bits from systemd. AFAIK, that's all dbus and Canonical AFAIK already has a shim layer which does the same thing on Upstart. But that's Upstart, that's not every single init system out there (what Ian is after).

As I see it, I'm highlighting, but it is up to distributions to do something with it (though I'll try and assist if reasonable).