Source: python-undetected-chromedriver
Version: 3.5.5-2
Usertags: pidof-without-procps
Dear maintainer(s) of python-undetected-chromedriver,
it appears that python-undetected-chromedriver 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
python-undetected-chromedriver
that use `pidof` at runtime;
* via the `Build-Depends:` field of python-undetected-chromedriver, 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 python-undetected-chromedriver, 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 python-undetected-chromedriver uses `pidof` due to the
following
code snippets:
```
path: python-undetected-chromedriver_3.5.5-2/undetected_chromedriver/patcher.py
exe_name = os.path.basename(exe_name)
if IS_POSIX:
r = os.system("kill -f -9 $(pidof %s)" % exe_name)
else:
r = os.system("taskkill /f /im %s" % exe_name)
```
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
