1.2.0-3 in the archive
build failed,
ours is 1.2.0-3+py315.2.
Nothing recorded is waiting on this one.
aborted,
1.2.0-3+py315.2,
as work request 1315841,
which ended in work request 1315843.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1315843.
Sent before this one:
1.2.0-3+py315.1.
A version that was sent is spent, whatever came of it.
| 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 |
| 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-09-07 |
ci.debian.net | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
1.2.0-3+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-09-21 12:39 |
1.2.0-3
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-20 21:22 |
1.2.0-3+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-09-20 21:28 |