On Tue, 2022-01-11 at 19:37 +0100, Paul Gevers wrote:
> So, I guess the text could be updated to reflect this? I *guess* the
> reason that the e-mail was sent was because the bug was closed with the
> upload. That resets the autoremoval timer (until the issue is fixed *in
> testing*). The scrip
Hi,
On 11-01-2022 17:11, Mattia Rizzolo wrote:
On Tue, Jan 11, 2022 at 05:00:59PM +0100, Diederik de Haas wrote:
*) https://tracker.debian.org/pkg/discover also (still) shows it as a high
priority problem, while the problem is already fixed/addressed.
As I've seen it on t.d.o quite a lot of tim
On Tue, Jan 11, 2022 at 05:00:59PM +0100, Diederik de Haas wrote:
> *) https://tracker.debian.org/pkg/discover also (still) shows it as a high
> priority problem, while the problem is already fixed/addressed.
> As I've seen it on t.d.o quite a lot of times, it's either a problem in
> tracker or w
On 11 January 2022 05:39:03 CET Debian testing autoremoval watch wrote:
> discover 2.1.2-9 is marked for autoremoval from testing on 2022-01-24
>
> It is affected by these RC bugs:
> 999249: discover: missing required debian/rules targets build-arch and/or
> build-indep https://bugs.debian.org/999
4 matches
Mail list logo
