Source: kpipewire
Version: 6.6.4-1
Usertags: pidof-without-procps
Dear maintainer(s) of kpipewire,
it appears that kpipewire 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 kpipewire
that use `pidof` at runtime;
* via the `Build-Depends:` field of kpipewire, 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 kpipewire, 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 kpipewire uses `pidof` due to the following
code snippets:
```
path: kpipewire_6.5.4-1/src/monitors/autotests/mediamonitortest.cpp
QProcess pidof;
pidof.start(QStringLiteral("pidof"), {QStringLiteral("pipewire")});
pidof.waitForFinished();
if (QString::fromUtf8(pidof.readAllStandardOutput()).toInt() == 0) {
pipewire.start(QStringLiteral("pipewire"));
```
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
