2.58-4 in the archive
build failed,
ours is 2.58-4+py315.2.
Nothing recorded is waiting on this one.
aborted,
2.58-4+py315.2,
as work request 1347150,
which ended in work request 1347159.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1347159.
Sent before this one:
2.58-4+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 |
| 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-25 |
ci.debian.net | not dated |
| has anybody reported this under the usertag? |
1 bug
somebody has already reported this under the round's usertag, so it is tracked; the tag is the only record connecting what was sent to what this tracks #1149309 repo: FTBFS against python 3.15 (Connection reset by peer) |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
2.58-4+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-09-25 03:23 |
2.58-4
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-07 15:10 |
2.58-4+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-09-07 19:19 |