Hi, AFAICT, this bug only affects systems where systemd-sysv is installed.
Setting its severity to grave will cause its removal from testing if no quick action is taken (as currently stated on the PTS) which is not fair for those still using (plain) sysvinit.
(Really) Fixing this bug shall require upstream fixing systemd-sysv which is probably not due soon I bet ;-).
I'm afraid that unfortunately netenv users will probably have to choose between netenv xor systemd-sysv at some point but for the moment (and probably beyond), it seems to me that an acceptable temporary fix would be to add a conflict with systemd-sysv to avoid the package removal and keeping this bug around as a reminder.
Arnaud, what do you think about it? phep -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
