Control: severity -1 minor
On Thu, 14 May 2026 01:25:01 +0200 Gioele Barabucci <[email protected]>
wrote:
It is believed that apt-cacher-ng uses `pidof` due to the following
code snippets:
```
path: apt-cacher-ng_3.7.5-1.1/tests/cmdline/apt-cacher-ng.sh
$exe foreground=0 logdir=$TMP CacheDir:$TMP port:$PORT pidfile=$TMP/x.pid
sleep 1
pidsAfter=$(pidof apt-cacher-ng)
test $(echo $pidsAfter | wc -w) -eq $(( $(echo $pidsBefore | wc -w) + 1 ))
for x in $pidsAfter ; do
path: apt-cacher-ng_3.7.5-1.1/tests/cmdline/apt-cacher-ng.sh
pidsBefore=$(pidof apt-cacher-ng)
$exe foreground=0 logdir=$TMP CacheDir:$TMP port:$PORT pidfile=$TMP/x.pid
sleep 1
```
Dear apt-catcher-ng maintainer,
d/rules disables dh_auto_test, no autopkgtests are present and the build
logs do not show the test script `apt-cacher-ng.sh` being run. For all
these reasons I believe you can close this bug without further action.
In the meantime I will reduce the severity of this issue to minor.
Regards,
--
Gioele Barabucci