On Tue, May 12, 2015, at 06:38, Andreas Henriksson wrote: > As Martin Pitt already mentioned in Bug#777113, I'm echoing here my > intention to NMU sysvinit. My changes (previously posted on mailing > lists / bugs) now pushed to the collab-maint repo: > > http://anonscm.debian.org/cgit/collab-maint/sysvinit.git/commit/?id=4974842b73ddc3417c9e79f33399f673e3e58c48 > http://anonscm.debian.org/cgit/collab-maint/sysvinit.git/commit/?id=a067f2dd75fef1aeadd1ff880876b7e46a48c9f8 > http://anonscm.debian.org/cgit/collab-maint/sysvinit.git/commit/?id=1b7d726b201b1ea522daadd92bbbbac9eeb317f3 > http://anonscm.debian.org/cgit/collab-maint/sysvinit.git/commit/?id=2abc7031f4a4b6f00a285ec630c9dbcfcc15a26b > > Please scream ASAP if you spot any problems or would like to abort the > non-maintainer upload which will be executed really soon (likely this > weekend).
I didn't notice any errors, but I am away from any suitably instrumented Debian box with a jessie/sid chroot ATM to test it myself. My main worry would be a multi-package update run (which includes sysvinit and util-linux, as well as other packages that have initscripts) where something needed by invoke-rc.d, update-rc.d or an initscript is missing at the time dpkg is running maintainer scripts. Other than that, it is just a matter of running this NMU through the usual tests (piuparts, install/remove/upgrade packages with initscripts, and a boot, reboot and shutdown test using VMs). I assume you already did that testing? -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique de Moraes Holschuh <h...@debian.org> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
