[Pkg-sysvinit-devel] Bug#751589: sysvinit-core: /sbin/init missing after switching from systemd to sysvinit

[Sven Joachim]

Control: reopen -1

Closing bugs which render the system unbootable seems a bit premature to me.

On 2014-06-14 17:03 +0200, Michael Biebl wrote:

> Am 14.06.2014 16:55, schrieb Sven Joachim:
>> Control: reassign -1 systemd-sysv 204-6
>> 
>> On 2014-06-14 16:18 +0200, Michael Gold wrote:
>> 
>>> Package: sysvinit-core
>>> Version: 2.88dsf-53.2
>>> Severity: critical
>>>
>>> After a failed switch to systemd today (Debian bug #751585), I tried to
>>> switch back to sysvinit but found /sbin/init missing after a reboot,
>>> which of course prevented the system from booting.
>>>
>>> /sbin was available in the emergency shell and contained some files, but
>>> 'init' wasn't there.  'dpkg -L sysvinit-core' ended at the line '/sbin'
>>> (i.e., it was missing /sbin/shutdown, /sbin/init, etc.).  I eventually
>>> figured out to run 'dpkg -i' on that .deb; this restored /sbin/init, and
>>> then I was able to boot the system normally.
>>>
>>> I've attached dpkg and apt logfiles, starting with the systemd
>>> installation.
>> 
>> Those show that sysvinit-core was unpacked with systemd-sysv still in
>> place which is bad because systemd-sysv Replaces sysvinit-core.  The
>> systemd-sysv package should declare a Conflicts rather than Breaks on
>> sysvinit-core to prevent this from happening.
>> 
>
> This is not going to happen as this conflicts with #748355.

#748355 is about the conflict with sysvinit, not with sysvinit-core.

> We are actually going to drop the Breaks.

Okay, then sysvinit-core must declare the necessary
"Conflicts: systemd-sysv".  Feel free to reassign back.

Cheers,
      Sven