3.13.3+dfsg-1 in the archive, ships a compiled extension
built,
ours is 3.13.3+dfsg-1+py315.d.1.
Rebuilding it releases 6449 packages waiting on it, as this stage last counted.
published,
3.13.3+dfsg-1+py315.d.1,
as work request 1278919.
| 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 bad, i386 bad, loong64 bad, ppc64el bad, riscv64 bad, s390x bad |
release.debian.org, from their ben tracker | 2026-09-16 04:49 UTC |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
3.13.3+dfsg-1+py315.d.1
|
arm64 | test | pass | rebuilt | named none | — | 2026-09-15 16:59 |
3.13.3+dfsg-1+py315.d.1
|
amd64 | test | pass | rebuilt | named none | — | 2026-09-15 16:42 |
3.13.3+dfsg-1
|
arm64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-15 15:46 |
3.13.3+dfsg-1
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-15 15:46 |
3.13.3+dfsg-1+py315.d.1
|
arm64 | build | pass | unknown | not read yet | — | 2026-09-15 16:58 |
3.13.3+dfsg-1+py315.d.1
|
amd64 | build | pass | unknown | not read yet | — | 2026-09-15 16:38 |
3.13.3+dfsg-1+py315.d.1
|
all | build | pass | unknown | not read yet | — | 2026-09-15 16:41 |