Control: tag -1 + unreproducible
On Fri, 05 May 2023 14:16:53 +, Holger Levsen wrote:
> On Fri, May 05, 2023 at 03:49:44PM +0200, Jérôme Bardot wrote:
> > That bug is currently blocking from using munin on not systemd systems.
> I'm not planning on supporting legacy initscripts myself. And
thx …
Le ven. 5 mai 2023 à 16:16, Holger Levsen a écrit :
>
> control: tags -1 + wontfix
> thanks
>
> On Fri, May 05, 2023 at 03:49:44PM +0200, Jérôme Bardot wrote:
> > That bug is currently blocking from using munin on not systemd systems.
>
> I'm not planning on supporting legacy initscripts
control: tags -1 + wontfix
thanks
On Fri, May 05, 2023 at 03:49:44PM +0200, Jérôme Bardot wrote:
> That bug is currently blocking from using munin on not systemd systems.
I'm not planning on supporting legacy initscripts myself. And despite tagging
this bug 'wontfix' for the time being I will
That bug is currently blocking from using munin on not systemd systems.
Hello, some news about that bug ?
I currently get the same error. (also without systemd)
Currently the post update conf fails on the post install script.
Package: munin-node
Version: 2.0.69-1~bpo11+1
Severity: normal
X-Debbugs-Cc: mnalis-debian...@voyager.hr
Dear Maintainer,
* What led up to the situation?
After upgrading from Stretch to Buster to Bullseye, munin-node (2.0.49-1)
refuses to start.
(Which was especially frustrating, as Debian
6 matches
Mail list logo