Bug#1055463: sysvinit-core: Please entirely remove SysVinit

Matthew Vernon matthew at debian.org
Tue Nov 7 09:58:10 GMT 2023


Hi,

On 07/11/2023 01:14, Patrik Schindler wrote:
> Am 07.11.2023 um 01:59 schrieb Thorsten Glaser <t.glaser at tarent.de>:
> 
>>> 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.

Yes, it's a Recommends: which means it'll be pulled in on most upgrades 
(I agree it would have been better to have got something into the 
release notes; I don't know if they are still taking updates for the 
bookworm release notes, but do feel free to propose some text for them).

If you find future init scripts missing that aren't in 
orphan-sysvinit-scripts and the relevant package maintainer isn't 
willing to restore them, do file a bug report (ideally with the 
requested details from the README - 
https://salsa.debian.org/matthew/orphan-sysvinit-scripts/ ) against 
o-s-s and we can get them into trixie.

I had thought we'd caught nearly all of the scripts from bookworm, but 
if there are missing ones there we could try and get a fix into the next 
point release.

[are we at the point where this bug report can be closed? I feel like 
there might be a bug report with patch if you want the release notes 
updating, and/or bugs for particular missing init scripts]

Regards,

Matthew



More information about the Debian-init-diversity mailing list