Dear maintainer(s) of tint2,

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

```
path: tint2_17.0.1-1.2/test/regression.py
    value = 0
  result = value * 1.0e-6
  p = run("./meminfo.py --detailed --private $(pidof tint2)", output=True)
  detailed, _ = p.communicate()
  return result, detailed
```

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

Regards,

Control: severity -1 minor


Dear maintainer(s) of tint2,

by looking at the source code of tint2 and at the logs of Salsa CI it
seems that this test is only run through test/update_test_status.sh, and
that script is not run as part of the build-time testsuite. It is also
not run by the autopkgtests.

You can thus probably close this bug report without further action.

In the meantime I'll downgrade the severity to minor.

Regards,