Dear Michael! Again I ask you to reconsider and put the init script back in. If that would be too much work for you, I am sure someone would be willing to provide a patch.
I like to remind you about the winning choice of last years GR¹. It is specifically labeled as: Option 2 "B: Systemd but we support exploring alternatives" Please note the "but we support exploring alternatives". Also look at the following excerpt of the choice: """ The Debian project recognizes that systemd service units are the preferred configuration for describing how to start a daemon/service. However, Debian remains an environment where developers and users can explore and develop alternate init systems and alternatives to systemd features. Those interested in exploring such alternatives need to provide the necessary development and packaging resources to do that work. Technologies such as elogind that facilitate exploring alternatives while running software that depends on some systemd interfaces remain important to Debian. It is important that the project support the efforts of developers working on such technologies where there is overlap between these technologies and the rest of the project, for example by reviewing patches and participating in discussions in a timely manner. """ Not only in my point of view the GR last year¹ does not mean that "systemd has won!". Especially the GR does not endorse "drop all init scripts". Additionally you provided no reason whatsoever for the removal of the init script in the changelog: """ network-manager (1.25.91-1) unstable; urgency=medium * New upstream version 1.25.91 (1.26 rc2) * Remove SysV init script -- Michael Biebl <[…]> Thu, 02 Jul 2020 01:17:08 +0200 """ And you did not answer to this bug report since almost a month except for setting its severity to "wishlist". Removing the init script breaks existing systems using something else than systemd together with Network Manager. This is a use case that worked for a long, long time. It still does work once the init script is copied back after removal. There is no warning in debconf, no explanation in README.Debian or NEWS.Debian. All current Debian Buster users with something else than systemd as PID 1 and with Network Manager would be left in the dark about why the upgrade broke their networking setup. On the other hand I do not see any benefit from removing the init script. All it caused up to now is further friction. If you have doubts about maintaining and bug fixing the init script, in case there are bugs, I am sure someone would be willing to do that. Current support for sysvinit, runit, elogind and other alternatives to Systemd and (some of) it's parts is pretty good in Debian, to a great extent thanks to the wonderful cooperation with the Devuan project. So please reconsider. [1] https://www.debian.org/vote/2019/vote_002 Thank you, -- Martin
signature.asc
Description: This is a digitally signed message part.
