1.1.2-2 in the archive, ships a compiled extension
waiting, waiting on astropy, healpy.
Rebuilding it releases 12 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 archive build this version? |
archive ftbfs
Debian's own rebuild of the version the archive carries fails too, so this failure is not the new interpreter's doing. It still blocks the transition: nobody can rebuild it until that is fixed. amd64 arm64 |
tests.reproducible-builds.org | not dated |
| does the release team track this? |
dependency level 8
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 unknown, arm64 unknown, armhf unknown, i386 unknown, loong64 unknown, ppc64el unknown, riscv64 unknown, s390x unknown |
release.debian.org, from their ben tracker | 2026-09-16 04:49 UTC |
No run in this phase yet — it is waiting.