Your message dated Tue, 16 Jun 2026 17:42:26 +0300
with message-id <[email protected]>
and subject line Re: Bug#1136606: virglrenderer uses pidof but does not depend
on procps
has caused the Debian Bug report #1136606,
regarding virglrenderer 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.)
--
1136606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1136606
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: virglrenderer
Version: 1.2.0-2
Usertags: pidof-without-procps
Dear maintainer(s) of virglrenderer,
it appears that virglrenderer 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 virglrenderer
that use `pidof` at runtime;
* via the `Build-Depends:` field of virglrenderer, 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 virglrenderer, 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 virglrenderer uses `pidof` due to the following
code snippets:
```
path: virglrenderer_1.2.0-2/perf-testing/Docker/run.sh
# sometimes one of these processes seems to crash or exit before, so
# check whether it is still
kill `pidof producer-gpu` || echo "producer-gpu was not running (anymore)"
kill `pidof traced_probes` || echo "traced_probes was not running (anymore)"
kill `pidof traced` || echo "traced was not running (anymore="
```
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 ---
On Thu, 14 May 2026 01:33:40 +0200 Gioele Barabucci <[email protected]>
wrote:
Source: virglrenderer
Version: 1.2.0-2
Usertags: pidof-without-procps
Dear maintainer(s) of virglrenderer,
it appears that virglrenderer uses `pidof` in its testsuite, or that
at least one of its binary packages uses `pidof` at runtime.
...
> It is believed that virglrenderer uses `pidof` due to the following>
code snippets:
```
path: virglrenderer_1.2.0-2/perf-testing/Docker/run.sh
# sometimes one of these processes seems to crash or exit before, so
# check whether it is still
kill `pidof producer-gpu` || echo "producer-gpu was not running (anymore)"
kill `pidof traced_probes` || echo "traced_probes was not running (anymore)"
kill `pidof traced` || echo "traced was not running (anymore="
```
Feel free to close this issue if this is a false positive (for example
if this code is in an unreachable code path).
This whole directory (perf-testing) is not used in debian in any way -
neither it is included in any binary package nor is used in test or
build.
Why do you conclude libvirglrenderer actually uses pidof? Is it merely
because it's referenced in one of the source files?
Closing this bug report as a false positive.
Thanks,
/mjt
--- End Message ---
