A package for orphaned sysvinit scripts

Martin Steigerwald martin at lichtvoll.de
Sat Jan 2 18:27:29 GMT 2021

Matthew Vernon - 02.01.21, 16:11:40 CET:
> While the TC has not yet ruled on #975075, my reading of the tea
> leaves is that they are not going to overrule the maintainer on
> removing the network-manager sysvinit script.
> Does anyone have an idea of which packages are affected? I imagine
> it's more than just network-manager?
> This means we need some way to provide these for our users. I hope
> that it will remain a minority of packages, and that most people will
> continue to keep their init scripts where they belong (IMO  ).

From a users point of view, I am considering to just switch this laptop
which uses Debian to Devuan. All of my other machines are running Devuan
already. I am just through with any conflict around that. I really don't
get why Michael Biebl removed the init script from Network Manager
package. Especially when I read this:

network-manager (1.28.0-2) unstable; urgency=medium

  * Demote libpam-systemd to Recommends.
    This allows users to use and experiment with other init systems. Such a
    setup is neither tested nor fully supported and users need to be aware
    that some functionality might be broken. (Closes: #921012)

If he does this one, why does he insist having the package go without an
init script? On the other hand I do not feel like arguing with him about

Of course it would still be good to have some solution for Debian users.

Hopefully some day there can be a real solution for this conflict in Debian.


More information about the Debian-init-diversity mailing list