Your message dated Thu, 14 May 2026 08:35:26 +0000
with message-id <[email protected]>
and subject line Bug#1136576: fixed in rr 5.9.0-9
has caused the Debian Bug report #1136576,
regarding rr 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.)
--
1136576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1136576
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: rr
Version: 5.9.0-8
Usertags: pidof-without-procps
Dear maintainer(s) of rr,
it appears that rr 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 rr
that use `pidof` at runtime;
* via the `Build-Depends:` field of rr, 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 rr, 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 rr uses `pidof` due to the following
code snippets:
```
path: rr_5.9.0-6/src/test/term_trace_cpu.run
done
rrpid=$(parent_pid_of $(pidof $EXE-$nonce))
# It's possible for this signal to be acted on before chew_cpu actually
path: rr_5.9.0-6/src/test/nested_detach_kill_stuck.run
done
rrpid=$(parent_pid_of $(pidof $NEST_EXE-$nonce))
echo " done. Delivering SIGTERM to $rrpid ..."
kill -TERM $rrpid
path: rr_5.9.0-6/src/test/nested_detach_kill.run
done
rrpid=$(parent_pid_of $(pidof $NEST_EXE-$nonce))
echo " done. Delivering SIGTERM to $rrpid ..."
kill -TERM $rrpid
path: rr_5.9.0-6/src/test/util.sh
if ! which pidof &> /dev/null; then
pidof() {
ps ax -o 'pid= exe=' | grep ' \(\|.*/\)'"$1"'$' | awk '{print $1}'
}
path: rr_5.9.0-6/src/test/x86/string_instructions_replay.run
for i in $(seq 1 30); do
sleep 0.05
kill -CHLD $rrpid $(pidof $TESTNAME-$nonce) >& /dev/null
done
path: rr_5.9.0-6/src/test/concurrent_signals.run
done
pid=$(pidof $TESTNAME-$nonce)
(for i in $(seq 1 1000); do sleep 0; kill -USR1 $pid; done) &
(for i in $(seq 1 1000); do sleep 0; kill -USR2 $pid; done) &
path: rr_5.9.0-6/src/test/term_trace_syscall.run
done
rrpid=$(parent_pid_of $(pidof $TESTNAME-$nonce))
echo " done. Delivering SIGTERM to $rrpid ..."
path: rr_5.9.0-6/scripts/signal-rr-recording.sh
}
for rr_pid in `pidof rr` ; do
if cat /proc/$rr_pid/cmdline | tr '\0' '\n' | head -n2 | tail -n1 | grep
-qz '\(^record$\)\|/' ; then
signal_descendants $rr_pid
path: rr_5.9.0-6/src/test/execve_loop.run
for i in $(seq 1 30); do
sleep 0.01
kill -CHLD $rrpid $(pidof $TESTNAME-$nonce) >& /dev/null
done
path: rr_5.9.0-6/src/test/ignored_async_usr1.run
echo " done. Delivering SIGUSR1 ..."
kill -USR1 $rrpid $(pidof $TESTNAME-$nonce)
# Wait for 'record' to actually terminate. Otherwise we might start
path: rr_5.9.0-6/src/test/thread_exit_signal.run
done
pid=$(pidof $TESTNAME-$nonce)
for i in $(seq 1 100); do
sleep 0.001
path: rr_5.9.0-6/src/test/term_trace_reset.run
sleep 0.01
rrpid=$(parent_pid_of $(pidof $TESTNAME-$nonce))
kill -TERM $rrpid >& /dev/null
path: rr_5.9.0-6/src/test/nested_detach_stop.run
done
sleep_pid=$(pidof $SLEEP_EXE-$nonce)
nested_rr_pid=$(parent_pid_of $sleep_pid)
echo " done. Delivering SIGSTOP to nested rr $nested_rr_pid ..."
```
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: rr
Source-Version: 5.9.0-9
Done: Stephen Kitt <[email protected]>
We believe that the bug you reported is fixed in the latest version of
rr, 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.
Stephen Kitt <[email protected]> (supplier of updated rr 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: Thu, 14 May 2026 09:53:12 +0200
Source: rr
Architecture: source
Version: 5.9.0-9
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt <[email protected]>
Changed-By: Stephen Kitt <[email protected]>
Closes: 1136576
Changes:
rr (5.9.0-9) unstable; urgency=medium
.
* Wrap and sort control files.
* Depend on procps for pidof. Closes: #1136576.
Checksums-Sha1:
ddbd70f0089cd2e412ea001c6407a34853e58673 1953 rr_5.9.0-9.dsc
f34a802104230c87fbb6d72d2879cd309160f756 14920 rr_5.9.0-9.debian.tar.xz
c03bb5cdad34d60ceb2bc9d1ab9453473a48d1f2 9893 rr_5.9.0-9_source.buildinfo
Checksums-Sha256:
98fc1ed084ce41f8f8980bd7f942a88bafebd02bfbcd87416689fc1e5bd8b6b5 1953
rr_5.9.0-9.dsc
4a90adda71a3ce30f504cd665ed53d606781ffd4c796fc7de62f799d46d9b057 14920
rr_5.9.0-9.debian.tar.xz
04f40eb9f29f35f4b0636d987991cece24668c3384cf21fe4eed23eed19cb8f9 9893
rr_5.9.0-9_source.buildinfo
Files:
81d710ae81e712d8ab141ad9c5065b4d 1953 devel optional rr_5.9.0-9.dsc
c3de8fe88e80421338d37d1d7d3b7a30 14920 devel optional rr_5.9.0-9.debian.tar.xz
b4aa63226101e0be0e2c59919173213f 9893 devel optional
rr_5.9.0-9_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmoFf4IACgkQgNMC9Yht
g5wnjxAAg34zbFNZ4sqj6xwbHGKIwScF/NdfU0150Y86hvNF+noRIWjm6k12BtuA
ecGA7bz9vqjIxak0gv6oSxF1kjhm4IDDv+jLf+tmXKg8X1ZDaVrbNzOitPZ6GuND
TlnU/C29p23qDnkqrBkQb4iu3xOd06pGcTgdxS7DDMi7GxhRSJZYwm5wOj3ZyV8S
fJLaTQC4CMMvZ1cQuniOb7hdwSJaMgB9LqWqT5ZXbIrpKHjr2nJdHXOZkdd9G81l
nm7sn7wo6GlTgUucPLPqxpJI2rI+918hvlpXR9rUV2sLLSdKo62dfgrfBxPW4uzV
FZUEIIeHGIa+BP8aq8zYEF8iy+qwudYuE1k28i4Frh+BJPB4hwXc+/ysuQ9/gGU5
izAUyVVsBw2H3ZGDGUXIFfRI/uHMtYhKEORmlBMFlTCXLX6skpaSNl/ZJkLQQ6I8
/ec3pja3Q1WlB6cQSZdVpzh9E9hkBP636S3YUBGDIn3eop/qLQvU5mI6AIstyCIZ
xMzVSljam6XRXsIqUq1OPL/et8x7awGz8gm6OYaQU4eRfWQfZ9IxU9X8hnCubXqd
yU/dsZ/xmqcyXKmwUTbbh8IasHnsjzCAGMRbRkD0bxYxtF6zfCJZDd5IQR6mCNCZ
wS1OU6MfO9HQmNe67a192bshC35/rRJ4xeHGzuHaM0n+hJuipo4=
=ZSNj
-----END PGP SIGNATURE-----
pgpUruuK2JJxq.pgp
Description: PGP signature
--- End Message ---
