1.14.2-3 in the archive
build failed,
ours is 1.14.2-3+py315.2.
Nothing recorded is waiting on this one.
aborted,
1.14.2-3+py315.2,
as work request 1347235,
which ended in work request 1347237.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1347237.
Sent before this one:
1.14.2-3+py315.1.
A version that was sent is spent, whatever came of it.
| Question | Answer | Said by | As of |
|---|---|---|---|
| Why did the build fail? |
unknown
The log was read and says nothing this tool recognises. These are the failures somebody has to look at. |
deps/11 | not dated |
| 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 |
tests.reproducible-builds.org | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
1.14.2-3
|
arm64 | test | pass | the archive's (reference arm) | named none | — | 2026-09-24 21:06 |
1.14.2-3
|
amd64 | test | pass | the archive's (reference arm) | named none | — | 2026-09-24 21:06 |
1.14.2-3+py315.2
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-25 03:29 |
1.14.2-3+py315.2
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-25 03:28 |
1.14.2-3
|
arm64 | test | pass | the archive's (reference arm) | named none | — | 2026-08-22 15:25 |
1.14.2-3
|
amd64 | test | pass | the archive's (reference arm) | named none | — | 2026-08-22 15:25 |
1.14.2-3+py315.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-08-22 17:08 |
1.14.2-3+py315.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-08-22 17:08 |