0.22.1+ds1-3 in the archive, ships a compiled extension
built,
ours is 0.22.1+ds1-3+py315.1,
waiting on python-aiohttp, python-psutil.
Rebuilding it releases 1 package waiting on it, as this stage last counted.
published,
0.22.1+ds1-3+py315.1,
as work request 1014703.
| 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. arm64 |
tests.reproducible-builds.org | not dated |
| 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. amd64, arm64, last run 2026-06-12 |
ci.debian.net | 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 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 |
|---|---|---|---|---|---|---|---|
0.22.1+ds1-3+py315.1
|
arm64 | test | pass | rebuilt | 3.13, 3.14, 3.15 | — | 2026-08-16 14:16 |
0.22.1+ds1-3+py315.1
|
amd64 | test | pass | rebuilt | 3.13, 3.14, 3.15 | — | 2026-08-16 14:10 |
0.22.1+ds1-3+py315.1
|
arm64 | build | pass | unknown | not read yet | — | 2026-08-16 14:11 |
0.22.1+ds1-3+py315.1
|
amd64 | build | pass | unknown | not read yet | — | 2026-08-16 14:06 |