Hi, On Fri, May 26, 2017 at 12:04:59PM +0200, John Paul Adrian Glaubitz wrote: > > > As the init system is a rather fundamental component of a Linux > > > distribution, it affects many other packages, directly or indirectly > > > and it's therefore too much of a burden to provide support for all > > > init systems available in Debian. Although runit is available in > > > Debian, it does not mean that it has to be fully supported. > > > > If an init system is shipped in a stable release, it has to be supported. > > Otherwise it should not be in a stable release. > > Well, there is also ulibc being shipped with Debian stable. Yet, when > someone tries to use it and breaks their system, it's not supported > either. So, I don't think this policy can be sweepingly applied to > every package.
There is no package named 'ulibc', so I guess that's a typo. If you meant uclibc, that package only ships uclibc-source, so installing that doesn't break anything. > > > A possible solution would be to modify the runit postinst scripts > > > in a way that it does not automatically overwrite the symlinks > > > for the the above commands until the machine has been rebooted > > > (e.g. by placing a script which is run only once after the system > > > has been first rebooted with runit) so that the 'poweroff' and > > > 'reboot' commands are still sent to systemd. However, the lack of > > > a reply of the runit maintainer to this particular bug report seems > > > to indicate that there is currently no interest for such a solution. > > > > If the maintainer isn't interested in making sure that this package works as > > expected, it isn't fit for a stable release... > > I fully agree. However, runit is one of the packages which is not > automatically removed. No. But it can be manually removed. > > > Thus, in order to prevent this bug report from blocking the release > > > of Debian Stretch, I have reduced its severity to 'normal'. You > > > are still welcome to propose a patch to address this issue though, > > > it's just not relevant for the upcoming Debian release. > > > > This is not a good reason to downgrade a bug. > > Again, Debian has decided to adopt systemd as the standard init > system, the same way we have decided to adopt glibc and the Linux > kernel as the standard C libraries and kernels. > > You really cannot expect a fundamental component like an init system > to be easily replace by the end user the same way they can swap their > default text editor. Well, in that case there shouldn't be a package that tries to swap the init system. If there is a package that provides the tools to do so, but lets you do it on your own, that's a different story. It will still allow you to break your system, but you can do that with lots of tools (certainly with your text editor). As there doesn't seem to be an easy way to get an acceptable runit-init package, which replaces the init system by just installing a package, I don't see how the current src:runit package can stay in stretch. If someone wants to keep it, the best option is probably to remove the runit-init binary package, so that the other binary packages can stay. As Roger noted, that would require an NMU to do so. I'd be happy to unblock such a change (if it happens in the next few days, given the release timing announced in https://lists.debian.org/debian-devel-announce/2017/05/msg00002.html). Cheers, Ivo
