0.71.0-2 in the archive
build failed,
ours is 0.71.0-2+py315.2.
Nothing recorded is waiting on this one.
aborted,
0.71.0-2+py315.2,
as work request 1346839,
which ended in work request 1346841.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1346841.
Sent before this one:
0.71.0-1+py315.1, 0.71.0-1+py315.2, 0.71.0-2+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-time-machine 3.5.0-3+py315.1: we publish 3.5.1-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 #1149337 python-datamodel-code-generator: FTBFS against python 3.15rc2 (ValueError: '3.15' is not a valid PythonVersion) |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
0.71.0-2+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-09-25 02:49 |
0.71.0-2
|
amd64 | test | fail | archive | 3.14, 3.15 | — | 2026-09-01 03:20 |
0.71.0-2+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-09-01 07:18 |
0.71.0-1
|
amd64 | test | pass | the archive's (reference arm) | 3.14 | — | 2026-08-26 21:02 |