Your message dated Sat, 16 May 2026 15:34:44 +0000
with message-id <[email protected]>
and subject line Bug#1136579: fixed in runit 2.3.1-4
has caused the Debian Bug report #1136579,
regarding runit uses pidof but does not depend on procps
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.)
--
1136579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1136579
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: runit
Version: 2.3.1-3
Usertags: pidof-without-procps
Dear maintainer(s) of runit,
it appears that runit uses `pidof` in its testsuite, or that
at least one of its binary packages uses `pidof` at runtime.
Historically, `pidof` was provided by the Essential package
`sysvinit-tools`, making an explicit dependency unnecessary. However
`pidof` will soon be moved to `procps` and will no longer be part of
the Essential set.
Please add an explicit dependency on `procps`:
* via the `Depends:` field of all binary packages of runit
that use `pidof` at runtime;
* via the `Build-Depends:` field of runit, if `pidof` is
used in tests run at build-time;
* via the `Depends:` field of `debian/control/tests`, if `pidof` is
used in autopkgtests.
To prevent any disruption for users of runit, please add
this dependency now, before `pidof` is moved from `sysvinit-utils` to
`procps`. Alternatively, you could remove all uses of `pidof`.
It is believed that runit uses `pidof` due to the following
code snippets:
```
path: runit_2.3.0-1/debian/contrib/lib/trigger_sv
# fi
# done
if [ -f /etc/runit/stopit ] && pidof runsvdir > /dev/null ; then
[ "$(id -u)" = 0 ] && kill -s ALRM 1 # force rescan to pick
changes in enabled/disabled service status
fi
path: runit_2.3.0-1/debian/contrib/lib/trigger_sv
echo "$defaultdir : directory not found, exit" && exit 1
fi
if [ ! -f /etc/runit/stopit ] && ! pidof -q runsvdir ; then
[ -e /etc/runit/verbose ] && echo "no runsvdir found, exit"
exit 0 # noop if runit is not init and there's no runsvdir
running
path: runit_2.3.0-1/debian/tests/init-switch
if pidof getty; then
echo "OK"
elif pidof fgetty; then
echo "OK"
else
```
Feel free to close this issue if this is a false positive (for example
if this code is in an unreachable code path).
Regards,
--
Gioele Barabucci
--- End Message ---
--- Begin Message ---
Source: runit
Source-Version: 2.3.1-4
Done: Lorenzo Puliti <[email protected]>
We believe that the bug you reported is fixed in the latest version of
runit, 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 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: Sat, 16 May 2026 15:46:15 +0200
Source: runit
Architecture: source
Version: 2.3.1-4
Distribution: unstable
Urgency: medium
Maintainer: Lorenzo Puliti <[email protected]>
Changed-By: Lorenzo Puliti <[email protected]>
Closes: 1136579
Changes:
runit (2.3.1-4) unstable; urgency=medium
.
* trigger-sv: drop pidof, use s-s-d (dpkg) instead (Closes: #1136579)
* quilt (patch 0020): use timeout for chpst -l (lock)
* add a runit script for cruft-ng
* invoke-run:
- update manpage, document user services
- revert chdir to /home/username for user-services for now
Checksums-Sha1:
4075ff2803096e74b32fd596e890e36cf2967156 2225 runit_2.3.1-4.dsc
5309d4c28f125b3731727db1183792afb4a84cb4 88056 runit_2.3.1-4.debian.tar.xz
28ae089b84839dd7f880f56958723768f8f40b90 6972 runit_2.3.1-4_amd64.buildinfo
Checksums-Sha256:
392a9483b078f0b1857a27d0e10a5db4a3723b6242cdb4fa8a858e94d6fe648a 2225
runit_2.3.1-4.dsc
442a85f709776b203cc23e4095876a4f77fad47d81f85f80fcd4f7b89ca483f3 88056
runit_2.3.1-4.debian.tar.xz
deb23b2028824f1bc9331d6170fd06cabd2aace92a4dd89d32e9cafb39f28663 6972
runit_2.3.1-4_amd64.buildinfo
Files:
058718c1ea335eeaaa4320c1c5f7c8f2 2225 admin optional runit_2.3.1-4.dsc
d511350cb88904e12fa480377b4942e1 88056 admin optional
runit_2.3.1-4.debian.tar.xz
4efb8a32d93a4340e3eeb33f131e3b38 6972 admin optional
runit_2.3.1-4_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE2ji91PGnrxOd1bVNxxYb07RU7gMFAmoIiSQACgkQxxYb07RU
7gN8QA/9F+zHMgF0You3coHtoXrv93tNRSzMIP3Nssde5/MKLAOTbyU5GUqBJAHt
M9u5EIL9sPRuxOctJsI1pmqbf/WPXBpySrwwJOxEpLt0xpdHoPOwvw50bRC/4oGx
t0E106Ic64puoKzNAiY/nrnS3oabGD9U0hlmXecNH/4uHPQC8jR1iKcr5vgvRh4F
U3KcUkL+nK6OD87aRJ0BcI2YPXON5ZJYoCMfWcLoZfcY2Nx7DeUXX/FzOVT81H6F
TsUQedX6QxaqhpZYEBc/17TOSCcNxxiRszy785XKqGw+FqrYLwsVtvsFF8k1g0Wa
s7gB0yKsHM1OEtR3jYLUQGIWf0Wxesm7l7L2DomCRtccfMkhFQr2NLz/FfVL1/7M
cf3nfpQGyVcFtKPfv9iQMF8EDA90aTYrIM+CGNUJcJwPwjMUWYc4U+W/x3nRx9bN
t4FbOzUvYzr+/6S02QyVRm2qsyHiEr5fni7pOaOeLDbDGeZ5yIK1/N69FtbfgXVK
Mf5B7zFsNGKhOTDpSMLOjjIpHACRVhTgFI2OIx4WVLVtTOJMJePa04ZGyWxoTo8D
pbr312fm4b3BCeckmsT+tzGxUQVEyfdEk3FQW8GDnawQI7uyna//xRbpiVyxMX+I
IZuBOEEUcR2jDFo31IAinApL954WxfGRnjfK6YolRdASDfGErGA=
=PXXc
-----END PGP SIGNATURE-----
pgp7BqR6bV_SK.pgp
Description: PGP signature
--- End Message ---
