1.5.29-1 in the archive
tests aborted,
ours is 1.5.29-1+py315.1.
Nothing recorded is waiting on this one.
published,
1.5.29-1+py315.1,
as work request 1453244,
which ended in work request 1453260.
Which turned out to be tests-aborted: the tests were stopped: work request 1453260.
Sent before this one:
1.5.26-2+py315.1, 1.5.27-1+py315.1, 1.5.27-1+py315.2, 1.5.28-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? |
superseded-dependency
Built against our own rebuild of a dependency, one generation back. The run is evidence, unlike an archive copy: re-run it against the current suite before reading the failure. python3-caio 0.9.24-1+py315.1: we publish 0.12.4-1+py315.1 |
deps/11 | 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 #1145094 (done) python-blockbuster: FTBFS building against python 3.15 |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
1.5.29-1+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-10-12 22:33 |
1.5.29-1
|
amd64 | test | pass | archive | 3.14, 3.15 | — | 2026-10-12 21:25 |
1.5.28-1+py315.1
|
amd64 | test | pass | rebuilt | named none | — | 2026-09-25 15:51 |
1.5.28-1
|
amd64 | test | pass | archive | 3.14, 3.15 | — | 2026-09-25 15:06 |
1.5.28-1+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-09-25 15:49 |
1.5.27-2+py315.3
|
amd64 | test | pass | rebuilt | named none | — | 2026-09-01 15:31 |
1.5.27-2+py315.3
|
all | build | pass | unknown | not read yet | — | 2026-09-01 15:29 |
1.5.27-1
|
amd64 | test | fail | archive | 3.14, 3.15 | — | 2026-08-27 16:29 |
1.5.27-1+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-08-27 20:07 |