[Pkg-sysvinit-devel] Bug#645540: Bug#729576: duplicate of bug #726763

[Andreas Cadhalpun]

Hi,

On 28.12.2013 02:07, Vincent Lefevre wrote:
> On 2013-12-22 23:30:21 +0100, Andreas Cadhalpun wrote:
>>>>> If GNOME developers want to require systemd as the init system,
>>>>> I don't see this as a reason not to add the dependency. Users
>>>>> are not forced to install GNOME packages. And if they want GNOME,
>>>>> they would have to accept the consequences about the init system.
>>>> The problem is the policy [1]:
>>>> "Essential is defined as the minimal set of functionality that must be
>>>> available and usable on the system at all times"
>>>> So removing an essential package is not really allowed by the policy.
>>> There's the same problem with systemd-sysv itself. So, I don't think
>>> it is against the policy. This point is more for tools handling
>>> package installation and removal, and also to avoid two essential
>>> packages conflicting each other.
>> I think it is not acceptable that the default Debian installer (for a
>> desktop system) does not install an essential package, which would be the
>> case, if gnome depended on systemd-sysv. Currently I think there is no
>> package that depends on systemd-sysv without alternative and systemd-sysv is
>> a package that actually does nothing else (as far as I can tell), but
>> replace sysvinit with a link to systemd.
>
> The latest change of sysvinit should solve this conflict issue,
> once systemd-sysv no longer conflicts with sysvinit, but with
> sysvinit-core:
>
> sysvinit (2.88dsf-44) unstable; urgency=low
> [...]
>    [ Steve Langasek ]
>    * Move sysvinit functionality into a new binary package, sysvinit-core,
>      and have sysvinit depend on an ORed list of the available
>      implementations of /sbin/init.  Since sysvinit is an Essential: yes
>      package, this is the only away to allow users to cleanly switch between
>      init systems without having to go through a multi-release-cycle
>      transition.  Closes: #728566.
>
>   -- Steve Langasek <vorlon at debian.org>  Thu, 26 Dec 2013 11:09:49 -0800

The package systemd-sysv should only break/replace sysvinit-core and not 
sysvinit (see bug #733240), which would solve bug #645540 as well.

After that gnome-shell and gdm3 should add a recommendation for 
systemd-sysv, since most people will want to use the functionality like 
suspend from menus, that needs systemd as PID 1, but occasionally some 
people may prefer to use sysvinit-core or upstart.

Best regards,
Andreas