On Mon, Feb 20, 2023 at 03:51:50PM +0100, Adrien Nader wrote:
> Due to the size of the queues, I decided to start with the oldest
> issues.
Out of interest, how did you identify these "oldest issues"? I happened to
spend some time on proposed-migration on Thursday, and all of the packages I
worked on are older than the oldest package on your list, AFAICS. (The
*youngest* package I worked on was node-object-inspect, which is currently
208 days old.)
> # sparse
> I'm under the impression that upstream doesn't run their own testsuite
> at the moment.
> For instance, there is a diagnostic which has been changed in 2019 in
> 2094267c7d36d8696897c509558fc63e8a695765 and new testcases have been
> added with that diagnostic but older ones have not been updated
> accordingly (the one failing because of that change has been created in
> 2018 and hasn't been changed since then).
> All in all this seemed to much for a +1 shift and I didn't act on the
> package.
>
> # blurhash-python
> I tried to reproduce the issue which occured on armhf but I didn't
> manage to. There were actually two different issues and that made me
> think the issues were unrelated to this package. Due to the size of the
> queues, I didn't ask for re-triggers.
This package has since migrated. I guess someone did retrigger and it
passed.
Please don't be shy about retriggering because of the queues; the tests get
run eventually...
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slangasek@ubuntu.com vorlon@debian.org
