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. The release notes should have mentioned this, but for some reason, no text made it there. >For Debian 11, there was no need for this package (for me!) and it's Me either, asides from nftables things still had init scripts there. In bookworm, “unimportant” packages like lvm lost their init scripts, and it’s getting m̲u̲c̲h̲ worse for trixie ☹ >Maybe you can understand my frustration. I don't intent to belittle >anyones efforts in keeping SysVinit alive on Debian, but the current >state of affair is a foul compromise to not confront maintainers: >Package-separate initscripts do not sound like a good idea but a >workaround for a political issue. When things become political, they >become messy. My experience. Yes, indeed. Personally, I’m sticking to bullseye for the next, uh six or so years with ELTS. But that’s no reason to give up the fight for diversity, as long as people are still doing that. Running testing or unstable with sysvinit is now out for normal people though. I dislike the having the init scripts separate very much, too. But it’s either that… bye, //mirabilos -- 15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)
