2.5.0-1 in the archive
build failed,
ours is 2.5.0-1+py315.1.
Nothing recorded is waiting on this one.
aborted,
2.5.0-1+py315.1,
as work request 1504909,
which ended in work request 1504911.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1504911.
Sent before this one:
2.1.0-1+py315.1, 2.2.0-1+py315.1, 2.3.0-1+py315.1, 2.4.2-1+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 |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
2.5.0-1
|
amd64 | test | pass | archive | 3.14, 3.15 | — | 2026-10-20 15:19 |
2.5.0-1+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-10-20 15:38 |
2.4.2-1+py315.1
|
amd64 | test | pass | rebuilt | named none | — | 2026-10-15 04:27 |
2.3.0-1
|
amd64 | test | pass | archive | 3.14, 3.15 | — | 2026-10-15 03:19 |
2.4.2-1+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-10-15 04:23 |
2.3.0-1+py315.1
|
amd64 | test | pass | rebuilt | named none | — | 2026-09-14 19:46 |
2.3.0-1
|
amd64 | test | pass | archive | 3.14, 3.15 | — | 2026-09-14 15:27 |
2.3.0-1+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-09-14 19:41 |
2.2.0-1+py315.1
|
amd64 | test | pass | rebuilt | named none | — | 2026-09-13 10:24 |
2.2.0-1
|
amd64 | test | pass | archive | 3.14, 3.15 | — | 2026-09-13 09:15 |
2.2.0-1+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-09-13 10:20 |
2.1.0-1+py315.1
|
amd64 | test | pass | rebuilt | named none | — | 2026-08-24 21:10 |
2.1.0-1+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-08-24 21:09 |