[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1050722: marked as done (bookworm-pu: package runit-services/0.5.5~deb12u1)

Your message dated Sat, 07 Oct 2023 09:59:41 +0000
with message-id <E1qp461-00A4Eh-0k@coccia.debian.org>
and subject line Released with 12.2
has caused the Debian Bug report #1050722,
regarding bookworm-pu: package runit-services/0.5.5~deb12u1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1050722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050722
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian.org@packages.debian.org
Usertags: pu
X-Debbugs-Cc: runit-services@packages.debian.org, plorenzo@disroot.org
Control: affects -1 + src:runit-services

[ Reason ]
The version in stable (0.5.4) is currently affected by #1033542,
where in most cases the dhclient service fails to start and syslog
is flooded with failure messages at a very high rate, hiding other
potentially relevant logs.
The flood is a consequence of runit supervision design: when a service
wanted status is 'up' and the service crashes, it's automatically
restarted after a 1 second grace time.

Bug #1033542 was filed with severity 'normal' during the freeze and
at the time I thought that it was not worth an unblock request; now,
given several complains I've received about this, I'm reconsidering.
Dhclient is enabled and started by default for runit-init users; it
may take time to notice the flood on syslog and even then, for a user
that is not expert in runit, it's not easy to understand what is causing it.

The attached debdiff is for a no change rebuild of the same version
that is currently in unstable/testing

[ Tests ]
I tested the fix personally and it solves the issue

[ Risks ]
Low

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
 * stop hardcoding eth1 in dhclient run file
 * adapt the check file for empty $INTERFACE

Regards,
Lorenzo

--- End Message ---
--- Begin Message --- 
Version: 12.2

The upload requested in this bug has been released as part of 12.2.

--- End Message ---
Reply to: