1.2.0-4 in the archive, ships a compiled extension
pending,
ours is 1.2.0-4+py315.1.
Rebuilding it releases 8 packages waiting on it, as this stage last counted.
published,
1.2.0-4+py315.1,
as work request 1090837.
| Question | Answer | Said by | As of |
|---|---|---|---|
| does the release team track this? |
dependency level 0
The release team's own tracker lists it, and their dependency level is how the transition is sequenced: a level cannot be read as done while anything below it is outstanding. Their question is what a package's binaries depend on, not what it ships, so their verdict and ours can disagree without either being wrong. amd64 bad, arm64 bad, armhf bad, i386 bad, loong64 bad, ppc64el bad, riscv64 bad, s390x bad |
release.debian.org, from their ben tracker | 2026-09-16 04:49 UTC |
| what did triage decide about the build? |
infrastructure
Somebody's decision about this failure, not a measurement. The runs beside it are free to disagree with it, which is why both are kept. arm64 test suite under qemu-aarch64; amd64 built fine (972271) |
whoever triaged it | 2026-08-31 16:00 UTC |
| Is this filed in Debian? |
#1144507
Filed by this round, or adopted from the BTS by its usertag. |
the tracker's own record | not dated |
| has anybody reported this under the usertag? |
1 bug
somebody has already reported this under the round's usertag, so it is tracked; the tag is the only record connecting what was sent to what this tracks #1144507 (done) brotli: forcing use of qemu in arm and arm64 |
the BTS usertag | not dated |
No run in this phase yet — it is pending.