Bug#981575: runit-sysv: postinst/postrm do not signal PID 1

2021-02-02 Thread Holger Just
Hi Lorenzo, Lorenzo wrote on 2021-02-02 00:38: > The good news is that I believe it's already fixed in unstable, in the > new package runit-run, see > > https://salsa.debian.org/debian/runit/-/commit/754e00a3f0eb016d809aefc02ceedbc9854b5e68 Ah, I wasn't aware of the new package structure in Bulls

Bug#981575: runit-sysv: postinst/postrm do not signal PID 1

2021-02-01 Thread Lorenzo
On Mon, 1 Feb 2021 18:08:38 +0100 Holger Just wrote: Hi, first of all, thanks for the detailed report :) > Package: runit-sysv > Version: 2.1.2-25 > > Before the split of runit-sysv from the runit package in stretch, > runit used to signal PID 1 after it has inserted or removed its > configur

Bug#981575: runit-sysv: postinst/postrm do not signal PID 1

2021-02-01 Thread Holger Just
Package: runit-sysv Version: 2.1.2-25 Before the split of runit-sysv from the runit package in stretch, runit used to signal PID 1 after it has inserted or removed its configuration in /etc/inittab in runit.postinst resp. runit.postrm. This behavior was apparently removed in 001cc301 [1] with the