#1136516 knot-resolver uses pidof but does not depend on procps

#1136516#5
Date:
2026-05-13 23:28:31 UTC
From:
To:
Dear maintainer(s) of knot-resolver,

it appears that knot-resolver 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 knot-resolver
  that use `pidof` at runtime;
* via the `Build-Depends:` field of knot-resolver, 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 knot-resolver, 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 knot-resolver uses `pidof` due to the following
code snippets:

```
path: knot-resolver_6.2.0-2/tests/packaging/interactive/workers.sh
fi
actual_processes="$(pidof kresd | wc -w)"
if [ "$actual_processes" -ne "$expected_workers" ]; then
	echo "Incorrect number of workers"
```

Feel free to close this issue if this is a false positive (for example
if this code is in an unreachable code path).

Regards,

#1136516#10
Date:
2026-05-14 08:25:08 UTC
From:
To:
Right, it does use pidof but only in its packaging test-suite in
tests/packaging/interactive/workers.sh