On Thu, 14 May 2026 01:25:37 +0200 Gioele Barabucci <[email protected]>
wrote:
it appears that cairo-dock 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 cairo-dock
that use `pidof` at runtime;
* via the `Build-Depends:` field of cairo-dock, 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 cairo-dock, 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 cairo-dock uses `pidof` due to the following
code snippets:
```
path: cairo-dock_3.5.1-2.1/src/gldit/cairo-dock-file-manager.c
{
int iPID = -1;
gchar *cCommand = g_strdup_printf ("pidof %s", cProcessName);
gchar *cPID = cairo_dock_launch_command_sync (cCommand);
```
Dear cairo-dock maintainer,
pidof is used by the code that implements the public API
`cairo_dock_fm_monitor_pid`. `cairo_dock_fm_monitor_pid` is not used
inside cairo-dock itself, but is used by a couple of plugins shipped by
cairo-dock-plug-ins.
Personally, I would add `Depends: procps` to cairo-dock-core, but adding
it to the plugins would also be OK, I suppose.
Kind regards,
--
Gioele Barabucci
