Package: tech-ctte Severity: Important When upgrading an old system installing certain packages, like network-manager and gdm3 systemd-sysv is installed changing the init system. These packages depend on libpam-systemd, which depends on systemd-sysv | systemd-shim. If systemd-shim is not installed systemd-sysv will be, and the init system changes the default to systemd-sysv, and changing PID 1.
Changing init system, i.e. PID1, should be warned about loudly by debconf. Not all users want to change init system when doing and upgrade, of course this should not happen (sometimes unnoticed by upgrading a lot of packages). For new installations the situation is different, systemd is the default init system. Nevertheless, perhaps even for new installations the user should be given a choice. At least on how to reinstall sysvinit-core after installing the default init system: systemd-sysv in the Debian Installer (DI) (if not solvable by other means in the DI). The bug on (and the discussion there) on systemd-sysv: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747535 has ping-ponged in severity and the systemd maintainers always downgrade the severity to wishlist and tagged it wontfix. The only way to resolve this issue is that the CTTE makes a decision on this matter. Other bugs related to this issue are: 760601 764186 746578 In summary, the CTTE is asked to make a decision on debconf warnings on: 1) Changing init system on upgrades (including sid) 2) Inform about alternate init systems for new installations Thank you for your attention! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
