On Sun, May 29, 2022 at 11:51 AM Christoph Biedl <debian.a...@manchmal.in-ulm.de> wrote:
> No doubt about that, but my time is too precious for advocacy. > And since I can neither understand nor reproduce the issue, there's > nothing left to do here. you misunderstand. i wasn't speaking of advocacy, merely explaining exactly how and why the issue was detected, so that you are aware of the context. sysvinit is still officially supported by debian. therefore if a package breaks when sysvinit is installed and in use, that's serious. i described how to install it so that you could install it and thus reproduce the issue. therefore, closing this bugreport is the wrong action to take. i leave it with you to re-open it. my role and responsibility is completed in raising the issue and in responding to questions as best i am able. l.
