It's against the runit source package in maverick. Can you confirm that the runsvdir process itself was still active in single user mode? The current package behaviour should have resulted in runsvdir being killed and not respawning, but the runsv processes and the services they were supervising still remaining alive. Any testing or feedback would be appreciated.
I've added a debdiff that should fix this issue here:
https:/ /bugs.launchpad .net/ubuntu/ +source/ runit/+ bug/245728
It's against the runit source package in maverick. Can you confirm that the runsvdir process itself was still active in single user mode? The current package behaviour should have resulted in runsvdir being killed and not respawning, but the runsv processes and the services they were supervising still remaining alive. Any testing or feedback would be appreciated.