1.19.1-1 in the archive
build failed,
ours is 1.19.1-1+py315.2.
Nothing recorded is waiting on this one.
aborted,
1.19.1-1+py315.2,
as work request 1347037,
which ended in work request 1347041.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1347041.
Sent before this one:
1.17.0-4+py315.1, 1.19.1-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 |
| 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 |
| 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 #1149331 python-yamlfix: FTBFS against python 3.15rc2 |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
1.19.1-1+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-09-25 03:15 |
1.19.1-1
|
amd64 | test | pass | archive | 3.14, 3.15 | — | 2026-09-11 21:21 |
1.19.1-1+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-09-11 22:28 |
1.17.0-4
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-08-25 21:19 |
1.17.0-4+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-08-26 01:00 |