Dear maintainer(s) of universal-ctags,

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

```
path: universal-ctags_6.2.1-1/Tmain/unreadable-input.d/run.sh
. ../utils.sh
if ! type pidof > /dev/null 2>&1; then
	# pidof is needed to find auditd.
	skip "pidof command is not available"


path: universal-ctags_6.2.1-1/Tmain/unreadable-input.d/run.sh
fi
if ! pidof auditd > /dev/null 2>&1; then
	# sudo expects auditd is running.
	skip "auditd is not running"
```

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

Regards,

Hello,
[...]

The test is run at build time and the build logs contains:

```
Testing unreadable-input
------------------------------------------------------------
skipped (auditd is not running)
Testing simple-pkgconfig as PkgConfig                       passed
```

If pidof where not available at all, the test code would simply bail
slighly before.... so no practical difference.

Either way, the test will be skipped - just for different reasons (pidof
not available or currently because auditd is not detected as running).

I think the bug report can thus simply be closed.

Someone might want to make the test not be skipped in the future, but
then they could add the needed dependencies at that time.

Regards,
Andreas Henriksson