Am 07.11.2023 um 02:28 schrieb Thorsten Glaser <t.gla...@tarent.de>:

>> 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).

Reiterating what I've stated in #1055466 in other words… leaving aside 
recommends-are-default, missing recommends IMHO should not half-break a system 
at upgrade time.

> 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.

Small but important. A system without (a running) logging daemon is not a 
proper Linux system. What exactly should pull in is probably a mere matter of 
taste.

> 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.

Well, I definitely got some bruises and I'm still contemplating about other 
distro options.

Should I open up another bug report for making o-s-s a hard dependency for (one 
of) the SysVinit packages?

>>> 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.

Sigh. That's why I hate politics. Technology can't fix what politics and 
half-cooked compromises has broken. And affected users stay behind with "WTF".

:wq! PoC

Reply via email to