25.7.0-3 in the archive, ships a compiled extension
pending.
Rebuilding it releases 6 packages waiting on it, as this stage last counted.
Nothing has been sent for this package in this stage. The stage is what a submission is recorded under, so another stage's is on that stage's page.
| Question | Answer | Said by | As of |
|---|---|---|---|
| does the release team track this? |
dependency level 5
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 unknown, i386 unknown, loong64 bad, ppc64el bad, riscv64 bad, s390x bad not in testing, so sid only |
release.debian.org, from their ben tracker | 2026-09-16 04:49 UTC |
| 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 #1145997 gpaw: FTBFS against python 3.15rc1 |
the BTS usertag | not dated |
No run in this phase yet — it is pending.