0.48.2-1.1 in the archive
build failed,
ours is 0.48.2-1.1+py315.d.1.
Nothing recorded is waiting on this one.
aborted,
0.48.2-1.1+py315.d.1,
as work request 1307196,
which ended in work request 1307198.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1307198.
Sent before this one:
0.48.2-1+py315.d.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 arm64 |
tests.reproducible-builds.org | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
0.48.2-1.1
|
arm64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-19 09:06 |
0.48.2-1.1
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-19 09:06 |
0.48.2-1.1+py315.d.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-19 11:59 |
0.48.2-1.1+py315.d.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-19 12:06 |
0.48.2-1.1+py315.d.1
|
all | build | fail | unknown | not read yet | — | 2026-09-19 12:03 |
0.48.2-1
|
arm64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-16 09:19 |
0.48.2-1
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-16 09:19 |
0.48.2-1+py315.d.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-16 10:43 |
0.48.2-1+py315.d.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-16 10:41 |
0.48.2-1+py315.d.1
|
all | build | fail | unknown | not read yet | — | 2026-09-16 10:41 |