On Tue, 7 Nov 2023, Patrik Schindler wrote: >>> I have sysvinit-core installed and orphan-sysvinit-scripts was not pulled >>> in automatically. >> Yeah, it’s not. > >As I'm learning from a discussion in bug #1055466, this is due to >orphan-sysvinit-scripts "only" being recommended and not a hard >dependency.
Recommends count, they are installed by default since, uh, lenny or so (a decision I still personally revert on all systems because that also includes transitive Recommends; instead I inspect the list of recommended packages manually). In trixie, o-s-s definitely should be a Depends of one of the packages (sysvinit? sysv-rc? or what?) but it was too late for bookworm, and it only affected users of a small number of packages there, IIRC. But yes, maybe that should be fixed in a stable upgrade, now that we know o-s-s is here to stay, it will be required in the next release, and there is visible user impact. Back then these things weren’t yet this clear. >> I dislike the having the init scripts separate very much, too. But it’s >> either that… > >… or try to reconcile Devuan efforts with Debian policies. Ugh, no. bye, //mirabilos -- <ch> you introduced a merge commit │<mika> % g rebase -i HEAD^^ <mika> sorry, no idea and rebasing just fscked │<mika> Segmentation <ch> should have cloned into a clean repo │ fault (core dumped) <ch> if I rebase that now, it's really ugh │<mika:#grml> wuahhhhhh
