Source: systemd-sysv Version: 204-10 Severity: critical Justification: breaks the whole system Control: retitle -2 sysvinit-core: for upgrade safety, systemd-sysv and sysvinit-core must be coinstallable
For safety of upgrades from wheezy to jessie, the process of upgrading packages and installing new ones *must not* change either the currently- running init or the init that will manage the system on the next boot. A transition away from sysvinit must only occur as a result of a deliberate sysadmin action with that specific effect, not as a side effect of any other operation. To achieve this, systemd-sysv and sysvinit-core must be coinstallable, with an alternatives-like mechanism for deciding which package actually provides init (if this can be done with actual alternatives for /sbin/init, that would be ideal, but I suspect it cannot be that simple). Other potential providers of /sbin/init should ideally also be included in this mechanism, but because the default-for-new-installations is changing in jessie from sysvinit to systemd, the cooperation of those two providers is more important than the others. severity:critical because, depending on how an installation is configured, an unanticipated conversion to systemd absolutely can cause the system to be unbootable, or fail to carry out its intended function (e.g. because a network server no longer starts on boot as intended). -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (501, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
