Response to active removal of initscripts

Thorsten Glaser t.glaser at
Thu Jul 2 18:19:58 BST 2020

On Thu, 2 Jul 2020, Martin Steigerwald wrote:

> This does not sound good. It makes me want to switch of my last Debian 
> based system to Devuan, unsubscribe from development related mailing 

As if Devuan had the resources to survive a sysvinit removal from Debian.

> lists of the Debian project and probably even cease my little packaging 
> effort I still do for Debian. Cause in the end I am seriously fed up with 

Even if you only use a downstream, packaging should be done upstream.

> this constant "If you do not defend it, then it is taken away from you" 
> that seems to be required for support of alternative init systems in 

Also, architectures (x32 especially).

> Debian. And this may be sooner than later if I see an update of Network 
> Manager removing the init script here as well, cause I rely on its 

This particular package is of no concern to me given I use ifupdown,
but others will follow its example…

> That disastrous GR from last year does not help either.


> I bet either someone musters up the courage to bring this up, again, on 
> debian-devel or debian-project or so… I think there are quite some 

The amount of people bringing it up is getting low, too.

> Debian developers though who do not agree with removing init scripts 
> like this.

Yes, but sheeple. Also, they might be more fed up with the
endless discussions…

> The other option would be to let the difference between Devuan and Debian 
> become bigger and fork any package where the Debian maintainer removes a 
> init script or something else required by other init systems.

As if…

tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn •
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

More information about the Debian-init-diversity mailing list