Your message dated Sun, 12 Jul 2026 18:35:09 +0000
with message-id <[email protected]>
and subject line Bug#1136518: fixed in kpipewire 6.7.2-1
has caused the Debian Bug report #1136518,
regarding kpipewire 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.)
--
1136518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1136518
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: kpipewire
Version: 6.6.4-1
Usertags: pidof-without-procps
Dear maintainer(s) of kpipewire,
it appears that kpipewire 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 kpipewire
that use `pidof` at runtime;
* via the `Build-Depends:` field of kpipewire, 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 kpipewire, 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 kpipewire uses `pidof` due to the following
code snippets:
```
path: kpipewire_6.5.4-1/src/monitors/autotests/mediamonitortest.cpp
QProcess pidof;
pidof.start(QStringLiteral("pidof"), {QStringLiteral("pipewire")});
pidof.waitForFinished();
if (QString::fromUtf8(pidof.readAllStandardOutput()).toInt() == 0) {
pipewire.start(QStringLiteral("pipewire"));
```
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 ---
Source: kpipewire
Source-Version: 6.7.2-1
Done: Aurélien COUDERC <[email protected]>
We believe that the bug you reported is fixed in the latest version of
kpipewire, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Aurélien COUDERC <[email protected]> (supplier of updated kpipewire package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 05 Jul 2026 00:05:03 +0200
Source: kpipewire
Architecture: source
Version: 6.7.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers <[email protected]>
Changed-By: Aurélien COUDERC <[email protected]>
Closes: 1136518
Changes:
kpipewire (6.7.2-1) unstable; urgency=medium
.
[ Aurélien COUDERC ]
* New upstream release (6.7.2).
* Update build-deps and deps with the info from cmake.
* Update symbols from build for 6.7.2.
* Add procps build dependency for tests using pidof. (Closes: #1136518)
Checksums-Sha1:
dbbf69d642cf098e10a90cad5000ceb4ebc1be73 3340 kpipewire_6.7.2-1.dsc
4c17cf11cd5f128e5c57d54e7b7e4bc817806229 156212 kpipewire_6.7.2.orig.tar.xz
2fb2a5ed44b7843753e15ca57e896d14301eee97 488 kpipewire_6.7.2.orig.tar.xz.asc
e516486ba8e6621c6943c0f09f980c4b7c57e680 19684 kpipewire_6.7.2-1.debian.tar.xz
64e09f0061595fdcd0f7f541b0806416b4b32f43 23891
kpipewire_6.7.2-1_amd64.buildinfo
Checksums-Sha256:
0fabed17358cdc00565df1965e2cc12a94f616848f675696f54332f3eb27baf3 3340
kpipewire_6.7.2-1.dsc
68bd246f4d403d3d7f49bd2ffcd4e0d12bc55fa81554533f750ac2e4bb5aa61e 156212
kpipewire_6.7.2.orig.tar.xz
f0ecb983f0c1426028adc7fba77101aa2339c5b4191a3a88df8c0763335665c4 488
kpipewire_6.7.2.orig.tar.xz.asc
fa6946c8a8ad0745e770e96fa925d939496955b01d8730c0eed24d916eaf9882 19684
kpipewire_6.7.2-1.debian.tar.xz
c9fec32b1b227f71edd61515080a08885d625ce23e9c1f41ad3adece22b90a6a 23891
kpipewire_6.7.2-1_amd64.buildinfo
Files:
a4834b24efc5586eaae491b7c7c60a27 3340 libs optional kpipewire_6.7.2-1.dsc
083661a1caa0577ebf938f9da0029503 156212 libs optional
kpipewire_6.7.2.orig.tar.xz
0c3972bc2221c2da3a2fda0c5d9e3abe 488 libs optional
kpipewire_6.7.2.orig.tar.xz.asc
99bf99de5cff85acc220e8ef2456f45f 19684 libs optional
kpipewire_6.7.2-1.debian.tar.xz
bebb3127ad4787878544a0a0ddfe89b7 23891 libs optional
kpipewire_6.7.2-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJHBAEBCgAxFiEEIW//QAAaDgcOKDsfcaflM/KRoyQFAmpQ9FQTHGNvdWNvdWZA
ZGViaWFuLm9yZwAKCRBxp+Uz8pGjJCceEACcLyTGND1/Ar/k5vEVHpi1WDgra/Vj
Tu2GiIe0Es11XUA3W2ZQBiuU7IDluEwnZFt34byMqxUfizv4GhEyfq8wt3WVwKZG
uEpYQ4chIo73zZIP9cGLqAmf7FR1QpaXDW4gB/N8hUq2MvQIovXtHfujW2RA06hI
RDRUL/AViaSvnqvW1cEOvSzQ3NJJXtvfqI9TUHftjRk14Mko8LyiMbZWBqFKyFTY
3ElwFSGYrU4+UNHgku65j5u071z7Z7S+Ws8xSwub35y9tfvrnbIOiyyzbsDLJy6S
ohhv8endMjnX0OTkQH7pwLVYDUfxC8hyp+m86a6cNdXHJNUnkvid9hcFOb1Ja8UJ
o8cM5yexNez8NZvwZxllddpK1XYVu3ppLBWzdE9s+jhCu/kFkVdtDhsNadDp+KDs
VWBgG0eUjKAw2ZL5XTF4qxii/gGO2yr1hsvXJA1RvYcyctnenJg2v3Sau0Og8RvZ
6XdEwE7JCfRf6/L+rXkmV6XK1gQ1mu0uJB6+1AwgMp1DMgFkp00CSMUWkEQwxSMN
S+xRQzx9UqHseLw/zJppNDn9aPC8cB77gtZtI4I/SQstLESRr02jqR1a1LOdeFVm
ezbJtjOncK5nmmgGU78a10nySMfHy8GSG9+nytSGqqNxPbt1ZweMWf8h4WsNE5lO
O2fHMZG01qSkDg==
=K17T
-----END PGP SIGNATURE-----
pgpKs9ZiqrPgU.pgp
Description: PGP signature
--- End Message ---
