Bug#727708: Processed: block 726763 with 727708

[Cameron Norman <camerontnorman@gmail.com>]

On Sat, Feb 1, 2014 at 3:48 PM, Uoti Urpala <uoti.urpala@pp1.inet.fi> wrote:

On Sat, 2014-02-01 at 15:24 -0800, Steve Langasek wrote:
> While I think the Depends: systemd should be dropped (via a split of the
> systemd package), that's not required for fixing the present problem.  That
> can be addressed by having gnome-settings-daemon Depends: systemd,
> systemd-shim | systemd-sysv.
>
> Would the GNOME maintainers be willing to upload such a change?  Or would
> they be ok with me NMUing gnome-settings-daemon for it?

I have the impression that systemd-shim diverts systemd files and you
don't want to have it installed if you're actually booting with systemd.
If this is accurate (I didn't check), then such a dependency change
would not be appropriate - the recommended way to install systemd is
still to NOT use systemd-sysv, while the above dependency would either
force installation of systemd-sysv or would incorrectly install
systemd-shim on systemd-booting systems.

 

I think there is a huge problem with recommending that systemd be installed by the user changing the init line in grub: a package can not depend on an init system being PID 1. Can a package be made that changes the init line to systemd? I think that is preferable, because it folows the upstream convention of installing systemd by changing the init value, while also allowing packages to depend on systemd being PID 1.

Nevertheless, there still needs to be a org-freedesktop-login1 virtual package. This will allow the systemd packagers to bump to systemd(-logind) v209 and let someone else maintain a systemd(-logind) v204 package in order to use logind without requiring systemd to be PID 1.

I think that, with these two packages (one virtual), the systemd packagers will be happy and GNOME can actually function properly with no intervention.

 
--

Cameron Norman