[From nobody Sun May 17 16:03:04 2026
Received: (at 1136603-done) by bugs.debian.org; 17 May 2026 15:01:30 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-7.2 required=4.0 tests=BAYES_00,DKIM_SIGNED,
 DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HAS_BUG_NUMBER,
 RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H5,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,
 SPF_PASS autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 26; hammy, 128; neutral, 22; spammy,
 0. spammytokens: hammytokens:0.000-+--H*Ad:N*Alexandre,
 0.000-+--H*F:N*Alexandre, 0.000-+--testsuite, 0.000-+--uwsgi,
 0.000-+--pidof
Return-path: &lt;niol@zincube.net&gt;
Received: from smtp3-g21.free.fr ([212.27.42.3]:47914)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from &lt;niol@zincube.net&gt;) id 1wOczi-002cep-1w;
 Sun, 17 May 2026 15:01:30 +0000
Received: from volyova.zincube.net (unknown [78.193.255.78])
 by smtp3-g21.free.fr (Postfix) with ESMTP id D208013F8B3;
 Sun, 17 May 2026 17:01:23 +0200 (CEST)
Authentication-Results: smtp3-g21.free.fr; dkim=pass (1024-bit key;
 unprotected) header.d=zincube.net header.i=@zincube.net header.a=rsa-sha256
 header.s=mail header.b=a6TuXKYJ; dkim-atps=neutral
Received: from localhost (unknown
 [IPv6:2a01:e34:ec1f:f4e0:32b0:1122:fe89:20c0])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
 key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256)
 (Client did not present a certificate)
 by volyova.zincube.net (Postfix) with ESMTPSA id 6EE0C29E0A2F;
 Sun, 17 May 2026 17:01:23 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zincube.net; s=mail;
 t=1779030083;
 h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
 to:to:cc:mime-version:mime-version:content-type:content-type:
 content-transfer-encoding:content-transfer-encoding:
 in-reply-to:in-reply-to:references:references;
 bh=iCYF3JrfoLkIouMenrQrSQ3Qkh5SjK8MMJAYw8ApZJw=;
 b=a6TuXKYJ2St3D3Qli3OdI5ZPy3oqUmEm0cFvB9uo6GiLHtPqDPRpZ3V39qQRUKaHtqVQg4
 oF+DaZH6NB2hzl20/wH/7ryjKHSCBbpe5PrP+AtKpxM4nJrLccT+3wgaHikv74/3fQXnnq
 rpuL2ynfKrzqRJNPoJ1BDbHhk52FfKY=
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Date: Sun, 17 May 2026 17:01:23 +0200
Message-Id: &lt;DIL1J5O572ID.36SWBG3H8UPH7@zincube.net&gt;
Subject: Re: [pkg-uWSGI-devel] Bug#1136603: uwsgi uses pidof but does not
 depend on procps
To: &quot;Gioele Barabucci&quot; &lt;gioele@debian.org&gt;, &lt;1136603@bugs.debian.org&gt;,
 &lt;1136603-done@bugs.debian.org&gt;
From: &quot;Alexandre Rossi&quot; &lt;niol@zincube.net&gt;
X-Mailer: aerc 0.21.0
References: &lt;72f276bb87d00169ce967a0c32a64a38@debian.org&gt;
In-Reply-To: &lt;72f276bb87d00169ce967a0c32a64a38@debian.org&gt;

Hi,

&gt; it appears that uwsgi uses `pidof` in its testsuite, or that
&gt; at least one of its binary packages uses `pidof` at runtime.
&gt;
&gt; path: uwsgi_2.0.31-3/tests/gh-shared.sh
&gt; path: uwsgi_2.0.31-3/tests/travis.sh
&gt;
&gt; Feel free to close this issue if this is a false positive (for example
&gt; if this code is in an unreachable code path).

Thanks for the hint, however this is not run by the build time test suite
or by debian-ci, thus closing.

Alex]