Your message dated Tue, 03 Feb 2026 19:18:36 +0000
with message-id <[email protected]>
and subject line Bug#1126699: fixed in runit-services 0.10.1
has caused the Debian Bug report #1126699,
regarding dbus.dep-fixer run script does not correctly check for existing
service definitions
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 [email protected]
immediately.)
--
1126699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126699
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: runit-services
Version: 0.10.0
With the line:
[ -d "/etc/sv/$name" ] && continue
the run script for dbus.dep-fixer attempts to check for the runit service
definition of the given service, so that it can be (re)started using init.d,
only if the runit definition does *not* exist, but a sysv init script in
/etc/rc2.d does exist.
This check is flawed because /etc/sv does not contain the whole set of services
known to runit. The runit-services package itself places services in
/usr/share/runit/sv/ and this directory must also be checked to ensure correct
behavior.
As it is now, it's possible that a service is started by runit directly, but
also started again as an init.d script triggered by dbus.dep-fixer because a
check of /etc/sv will not find that service (it is instead defined in
/usr/share/runit/sv/) This kind of double-start can cause issues and race
conditions.
The simplest fix is to check both directories, though even this is imperfect.
For a related bug about checking the existence of runit services so that the
equivalent init.d scripts are/aren't started, see #1022837.
--- End Message ---
--- Begin Message ---
Source: runit-services
Source-Version: 0.10.1
Done: Lorenzo Puliti <[email protected]>
We believe that the bug you reported is fixed in the latest version of
runit-services, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Lorenzo Puliti <[email protected]> (supplier of updated runit-services
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 03 Feb 2026 19:11:04 +0100
Source: runit-services
Architecture: source
Version: 0.10.1
Distribution: unstable
Urgency: medium
Maintainer: Lorenzo Puliti <[email protected]>
Changed-By: Lorenzo Puliti <[email protected]>
Closes: 1126699
Changes:
runit-services (0.10.1) unstable; urgency=medium
.
* dbus-dep.fixer: correctly test for existing services definition
(Closes: #1126699)
Checksums-Sha1:
c95663c548822cad1311cc6d4cca4a5489106b16 1714 runit-services_0.10.1.dsc
098bcab7d18748bd274db7d969d33b3a3486853a 21644 runit-services_0.10.1.tar.xz
bf01e9f14ead0161f6f45efddcefdacc50a7858a 5975
runit-services_0.10.1_amd64.buildinfo
Checksums-Sha256:
02baff968b7099aed6df68157e3820bb3632add369ace5f686ed1ca54f158315 1714
runit-services_0.10.1.dsc
2fb6de5318fb5287c4778c756904bd72d55718696ed935a2807e229b6e19858f 21644
runit-services_0.10.1.tar.xz
de5de18414df084b793f7c2cf6a50d3d0a49746346a47de82642914095b7db57 5975
runit-services_0.10.1_amd64.buildinfo
Files:
2e4116c215ba08eaa680df8e25d51a7b 1714 admin optional runit-services_0.10.1.dsc
f8c162313572bb1158dca520fa84e828 21644 admin optional
runit-services_0.10.1.tar.xz
372ada62be69e249b1091118f9c1a1e3 5975 admin optional
runit-services_0.10.1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE2ji91PGnrxOd1bVNxxYb07RU7gMFAmmCPykACgkQxxYb07RU
7gPaUw/+MdoYEsn+V0zyJohPzIE3sFEvr0zEsCa9BKLTP/V7z+9Kfw3qTwyqMpXJ
WJ+wwR6sK5qCU9kbfBhdhjx7sEAy0AoD8Bc16Y2MNmvBXQTF84M8cpzqilbrYM+8
JY4E+XoJ2gHiBBDR1b+6tOBB5LINLyuj4EMWqoOSYEyQtPbmPTENoZO3fc7kNz6J
ZVfyaefyJFkB9bYFwF4lIWtSO98EJ/hYen+aqqaXSYsszVVpA6pziWwqUvpyYNum
5FYWkEmcbhh/BMWsuGYe/REEWpTxv9iHjdx0Edt7HzOVWeoHbC15a8mP8XeFK+Xj
DE2/6L9rGXgyWmJklaJYjxlpjJPw9o1xBEwaHS+kU4Puo3KzzIj/fofu0HllAPmI
r41I/M4BMvg+p+V7iwEwHzM8DpEmGRcDB/6ZTKNsp9PFpV3SoVp2fgcxwdDf3Fbz
uNBwg2cgPn5uBMLKPwSDHffIQyLqsgLRYSo7PZGMGNyoeI3VCZkZvcQNE39Ylx05
0lGOmyzQ/izicej54nl3ciemB7Y2VSv4dCxw9j0wqhr9fzf6RkkZdZjuBI4SSFa2
Rs8xNe4LW+15GSFKEI8j+d6Z8dlT4Xs2Aq5uWbpQbvu/DwueC6XcPXaCB6TXhkWb
FUX60FoZaMZfSfw3zKi/9Pj5zIYreXje6s0KTKJXdtqfCrce6co=
=Xr/+
-----END PGP SIGNATURE-----
pgpWYjkrXvDb1.pgp
Description: PGP signature
--- End Message ---
