2024.2.1-3 in the archive, ships a compiled extension
tests failed,
ours is 2024.2.1-3+py315.d.1.
Nothing recorded is waiting on this one.
published,
2024.2.1-3+py315.d.1,
as work request 1287114.
| Question | Answer | Said by | As of |
|---|---|---|---|
| do Debian's own tests pass? |
archive tests fail
Debian's own tests for this package fail in unstable, so this failure is not the new interpreter's doing. debci answers about the source rather than about the version we rebuilt, which is why the date its run happened is shown. arm64, last run 2026-04-01 |
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 unknown, armhf unknown, i386 unknown, loong64 unknown, ppc64el unknown, riscv64 unknown, s390x unknown not in testing, so sid only |
release.debian.org, from their ben tracker | 2026-09-16 04:49 UTC |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
2024.2.1-3+py315.d.1
|
amd64 | test | fail | rebuilt | named none | — | 2026-09-16 13:41 |
2024.2.1-3
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-16 09:19 |
2024.2.1-3+py315.d.1
|
amd64 | build | pass | unknown | not read yet | — | 2026-09-16 13:38 |