Control: reassign -1 systemd-sysv Control: retitle -1 Add Conflicts against sysv-rc, insserv and startpar
Hi Erwan On Tue, 04 Jun 2024 12:58:27 +0200 Erwan David <er...@rail.eu.org> wrote:
Package: console-setup-linux Version: 1.227 Severity: normal When upgrading, I get following error message: Setting up: console-setup-linux (1.227) insserv: FATAL: service mountkernfs has to be enabled to use service keyboard-setup.sh I see that /etc/init.d/keyboard-setup.sh has # Required-Start: mountkernfs mountkernfs is in initscripts package, but console-setup.sh does not depends on it. So either this Required-Start should be removed, either the dependency should be added.
No such dependency should be added, as it's unnecessary and counterproductive. See below
..
Init: systemd (via /run/systemd/system)
You are using systemd as your active init. I'm quoting the stretch release notes here:
5.1.7. SysV init related packages no longer required
After the switch to systemd as default init system in Jessie and further refinements in Stretch, various SysV related packages are no longer required and can now be purged safely via apt purge initscripts sysv-rc insserv startpar
So, please make sure to purge those 4 packages and the problem should be gone.
At this point, I'd say the systemd-sysv package, which already has a Conflicts against "sysvinit-core, initscripts, orphan-sysvinit-scripts" should probably be extended to include sysv-rc insserv and startpar as well, so those packages can no longer be installed by accident. Those packages are unnecessary under systemd and as you've seen do more harm than good.
I'll leave that up to Luca to decide (if you don't agree, please close as wontfix)
Michael
OpenPGP_signature.asc
Description: OpenPGP digital signature
