On Sun, 01 Mar 2026, Don Armstrong wrote:
> Hrm; that's concerning. I have some theories, but I need to look into
> it more. [My first thought is that for some reason when bugscan ran,
> the package showed up as absent in unstable, so the versioning
> incorrectly indicated that the bug wasn't present in unstable, but I
> need to look at this more closely to see if that's what is going on.]
I'm now able to replicate this by running make-britney-counts on the
appropriate status file. I'm not sure why the code is failing for that
particular status and not failing for others, but I will check it out
as soon as I can.
$ for a in /srv/bugs.debian.org/bugscan/stati/status-20260226*; do
/srv/bugs.debian.org/bugscan/make-britney-counts -S $a; for b in
britney/{testing,unstable}{,-nr}; do mv $b ${b}-$(basename $a); done;
$ (cd britney; grep -l 1080757 *)
[...]
unstable-nr-status-202602261850
unstable-nr-status-202602261950
unstable-nr-status-202602262050
unstable-nr-status-202602262250
unstable-nr-status-202602262350
[...]
--
Don Armstrong https://www.donarmstrong.com
Le temps est un grand maître, dit-on; le malheur est qu'il soit un
maître inhumain qui tue ses élèves.
Time is a great teacher, but unfortunately it kills all its pupils.
-- Hector Berlioz
