2025.1.2~dfsg-1 in the archive, ships a compiled extension
pending,
ours is 2025.1.2~dfsg-1+py315.1.
Rebuilding it releases 2 packages waiting on it, as this stage last counted.
published,
2025.1.2~dfsg-1+py315.1,
as work request 1240242.
| Question | Answer | Said by | As of |
|---|---|---|---|
| does Debian's own test suite pass? |
not tested by debian
Debian runs no autopkgtest for this, so we have no independent baseline: nothing here distinguishes a failure this interpreter caused from one the package always had |
ci.debian.net | not dated |
| 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 unknown, ppc64el bad, riscv64 unknown, s390x unknown not in testing, so sid only |
release.debian.org, from their ben tracker | 2026-09-16 04:49 UTC |
No run in this phase yet — it is pending.