Am 06.11.2023 um 21:20 schrieb Matthias Geiger <werdah...@riseup.net>:
> This is caused by package maintainers just dropping init scripts, and not > honoring the GR about init systems in Debian. May I ask you to elaborate? What is GR? > The init-diversity team has been putting a lot of work into maintaining > sysvinit and related packages; please appreciate the effort they are putting > in. > > sysvinit (or openRC, in my case) is still usable with debian. The dropped > scripts are provided by the orphan-sysvinit-scripts page. I have sysvinit-core installed and orphan-sysvinit-scripts was not pulled in automatically. In fact, I wasn't aware about orphan-sysvinit-scripts until just now. I would have expected something that important to be mentioned in the "issues" documentation: https://www.debian.org/releases/stable/amd64/release-notes/ch-moreinfo.en.html For Debian 11, there was no need for this package (for me!) and it's also not mentioned in the bullseye documentation: https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information.en.html Bottom line: Something about dependencies went wrong in an unexpected way. The first time that it had such grave impact. I'm using Debian since 3.0 and was very happy that system upgrades were rather painless. Until now. > While some people would be probably happy to see sysvinit go it'd be a big > loss for debian at whole. I don't *want* it to go. In fact, I want to have it. But in a proper state. I also don't want to experience following the documentation, upgrade my machines(s), and be faced with an unknown amount of services not coming up, in the end costing me a whole day to wade through conffiles, with questionable changes being unloaded to the sysadmin (the master/slave/whitelist/blacklist discussion) and discovering that half of the system just doesn't come up because of maintainer's neglect of SysVinit. ~ $ dpkg -l |wc -l 1315 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. :wq! PoC
