seeking advise: runit-init and 'protected: yes'

Lorenzo plorenzo at disroot.org
Tue Mar 18 22:09:03 GMT 2025


Matthew,

thanks for sharing your opinion.

Best Regards,
Lorenzo


On Mon, 17 Mar 2025 22:47:12 +0000
Matthew Vernon <matthew at debian.org> wrote:

> I think if you think it's appropriate to add protected: yes to 
> runit-init, then you can do so. I don't think the TC bug you refer to
> is really relevant; it was about how much gatekeeping it was
> appropriate for the init metapackage maintainers to do. I think if
> you wanted to try and get runit-init into the dependencies of the
> init metapackage, it'd be a different conversation (and particularly,
> whether the bugs in runit that were identified in #838480 got fixed).
> 
> While the policy discussion on protected: yes hasn't concluded in 
> #872587 it still seems to me that runit-init is within the 
> likely-intended scope of protected: yes - if someone has installed it
> as their init system, they want it to be hard to accidentally remove
> it again.
> 
> Regards,
> 
> Matthew




More information about the Debian-init-diversity mailing list