[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Lots of buggy packages propagated to trixie today (?)



On 2023-10-22 13:43:18 +0100, Adam D. Barratt wrote:
> On Sun, 2023-10-22 at 14:37 +0200, Sebastian Ramacher wrote:
> > On 2023-10-22 13:20:43 +0200, Santiago Vila wrote:
> > > Hello.
> > > 
> > > It is just me, or lots of packages that were autoremoved
> > > from testing have propagated to testing again this night?
> > > 
> > > Example: "broker" has #1037597, however:
> > > 
> > > $ rmadison  broker
> > > broker     | 1.4.0+ds1-1   | oldstable      | source
> > > broker     | 1.4.0+ds1-1   | stable         | source
> > > broker     | 1.4.0+ds1-1   | testing        | source
> > > broker     | 1.4.0+ds1-1   | unstable       | source
> > > broker     | 1.4.0+ds1-1   | unstable-debug | source
> > 
> > Don't know yet why this happened. For that run, broker was marked as
> > BLOCKED but was still tried.
> 
> Depending on exactly which run, at a guess this is related to:
> 
> adsb@buxtehude:~$ ls -ltr /srv/bugs.debian.org/bugscan/stati | tail -n10
> -rw-r--r-- 1 debbugs debbugs  716663 Oct 22 02:52 status-202310220250
> -rw-r--r-- 1 debbugs debbugs    9865 Oct 22 03:50 status-202310220350
> -rw-r--r-- 1 debbugs debbugs  715452 Oct 22 04:50 status-202310220450
> -rw-r--r-- 1 debbugs debbugs  715452 Oct 22 05:50 status-202310220550
> -rw-r--r-- 1 debbugs debbugs  715452 Oct 22 06:50 status-202310220650
> -rw-r--r-- 1 debbugs debbugs  715823 Oct 22 07:51 status-202310220750
> -rw-r--r-- 1 debbugs debbugs  716262 Oct 22 08:51 status-202310220850
> -rw-r--r-- 1 debbugs debbugs  718794 Oct 22 09:52 status-202310220950
> -rw-r--r-- 1 debbugs debbugs  717317 Oct 22 10:50 status-202310221050
> -rw-r--r-- 1 debbugs debbugs  717694 Oct 22 11:51 status-202310221150
> 
> The small file from 03:50 only seems to contain bugs relating to
> pseudo-packages, based on a quick visual scan.

That would fit the time. b1/britney only checks for empty files.

Adding owner to the loop: Don, any idea what caused the RC bugs export
to miss all the non-pseudo package RC bugs? Would it be possible to fail
the export in such a case instead of providing partial RC bug data?

Cheers
-- 
Sebastian Ramacher


Reply to: