Your message dated Tue, 07 Jul 2026 08:22:16 +0200 with message-id <2206464.bB369e8A3T@grummly> and subject line Re: Bug#1136596: systemsettings uses pidof but does not depend on procps has caused the Debian Bug report #1136596, regarding systemsettings uses pidof but does not depend on procps to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1136596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1136596 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: systemsettings Version: 4:6.6.4-1 Usertags: pidof-without-procps Dear maintainer(s) of systemsettings, it appears that systemsettings 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 systemsettings that use `pidof` at runtime; * via the `Build-Depends:` field of systemsettings, 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 systemsettings, 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 systemsettings uses `pidof` due to the following code snippets: ``` path: systemsettings_4:6.5.4-1/appiumtests/apptest.py for _ in range(10): try: subprocess.check_call(["pidof", "systemsettings"]) except subprocess.CalledProcessError: break ``` 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
--- End Message ---
--- Begin Message ---Le jeudi 14 mai 2026, 01:33:06 heure d’été d’Europe centrale Gioele Barabucci a écrit : > Dear maintainer(s) of systemsettings, Hi, > it appears that systemsettings 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. > It is believed that systemsettings uses `pidof` due to the following > code snippets: > > ``` > path: systemsettings_4:6.5.4-1/appiumtests/apptest.py > for _ in range(10): > try: > subprocess.check_call(["pidof", "systemsettings"]) > except subprocess.CalledProcessError: > break > ``` we don’t currently run appiumtests (appium not packaged in Debian) so closing. Happy hacking, -- Aurélien
--- End Message ---
