Control: retitle -1 runit - default installation can force init switch Control: tag -1 moreinfo
Hi, Bastian Blank: > An installation attempt on a default system (with recommends enabled) of > runit wants to replace the installed init: thanks for reporting this, however I can't reproduce. I'm testing in a chroot freshly build with debootstrap as following # debootstrap --arch amd64 sid ./amd64Sid http://deb.debian.org/debian then chroot into it, make sure systemd and systemd-sysv are installed ====inside the chroot===== root@lorenz:/# dpkg -l | grep systemd ii libnss-systemd:amd64 245-2 amd64 nss module providing dynamic user and group name resolution ii libpam-systemd:amd64 245-2 amd64 system and service manager - PAM module ii libsystemd0:amd64 245-2 amd64 systemd utility library ii systemd 245-2 amd64 system and service manager ii systemd-sysv 245-2 amd64 system and service manager - SysV links root@lorenz:/# apt-config dump | grep Recommends APT::Install-Recommends "1"; #first attempt# root@lorenz:/# apt install runit Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: sysuser-helper Recommended packages: runit-sysv | runit-init | runit-systemd The following NEW packages will be installed: runit sysuser-helper 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 131 kB of archives. After this operation, 503 kB of additional disk space will be used. Do you want to continue? [Y/n] #second attempt, try to force the install of runit-sysv# root@lorenz:/# apt install runit runit-sysv Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: runit-sysv : Depends: sysvinit-core but it is not going to be installed E: Unable to correct problems, you have held broken packages. #third attempt, really try harder# root@lorenz:/# apt install runit runit-sysv sysvinit-core Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libnss-systemd Use 'apt autoremove' to remove it. The following additional packages will be installed: initscripts insserv psmisc startpar sysuser-helper sysv-rc Suggested packages: bootchart2 bootlogd The following packages will be REMOVED: libpam-systemd systemd-sysv The following NEW packages will be installed: initscripts insserv psmisc runit runit-sysv startpar sysuser-helper sysv-rc sysvinit-core 0 upgraded, 9 newly installed, 2 to remove and 0 not upgraded. Need to get 696 kB of archives. After this operation, 1339 kB of additional disk space will be used. Do you want to continue? [Y/n] ============================ To remove systemd-sysv you need to specify a Recommend of runit and a dependency of the Recommend: it looks pretty safe to me. I've tested also in a Vbox machine with Debian Sid and systemd as init, and I got the same result, except the list of removed packages in the third attempt is huge. Bastian, do you have any idea of why there is this difference? Are you able to reproduce an output like in message#5 within a a minimal chroot install as I have done above? Regards, Lorenzo
