Bug#1102538: unblock: glib2.0 blocked by openjdk-25 autopkgtest on riscv64
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: glib2.0@packages.debian.org, openjdk-25@packages.debian.org, debian-riscv@lists.debian.org, debian-ci@lists.debian.org
Control: affects -1 + src:glib2.0 src:openjdk-25
User: release.debian.org@packages.debian.org
Usertags: unblock
glib2.0_2.84.1-1 is currently not migrating, and if I'm reading the
excuses correctly, it's waiting for a successful autopkgtest run on
<https://ci.debian.net/packages/o/openjdk-25/testing/riscv64/> with the
proposed glib2.0. However, most testing attempts since 2025-03-25 (and
several before that) have timed out on riscv64.
This is preventing a CVE fix in glib2.0 from migrating (although
admittedly it is a rather tenous CVE, involving parsing a text date/time
that is more than 2GB of text).
Would it be possible to stop waiting for this particular test, or
alternatively apply a longer timeout on riscv64 for openjdk-25, until
riscv64 gets some faster CI workers?
(glib2.0's excuses entry cites a piuparts regression as the reason for
not migrating, but I think that might not really be true, because
https://piuparts.debian.org/sid/source/g/glib2.0.html doesn't list any
unsuccessful tests. Perhaps the machinery is confused by the existence
of a udeb, which can't be piuparts-tested?)
smcv
Reply to: