2.8.0-1 in the archive
build failed,
ours is 2.8.0-1+py315.2.
Nothing recorded is waiting on this one.
aborted,
2.8.0-1+py315.2,
as work request 1347051,
which ended in work request 1347062.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1347062.
Sent before this one:
2.8.0-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-psutil 7.1.0-1.1+py315.2: we publish 7.2.2-1+py315.1 |
deps/11 | not dated |
| Which known interpreter change does this failure show? |
tests-failed
the test suite failed, cause not narrowed. The tests failed under the new interpreter and nothing here recognises why. =================================== FAILURES =================================== |
deps/11 | not dated |
| was the interpreter under test installed? |
no
its chroot had a different Python installed instead, so its failure is about whatever that one is: these take their interpreter from the default rather than from pybuild python3.14_3.14.7-4 |
the build log's installed set | 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 arm64 |
tests.reproducible-builds.org | 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, last run 2026-09-07 |
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 #1149312 pytorch-geometric: FTBFS against python 3.15 (several test errors) |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
2.8.0-1+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-09-25 03:19 |
2.8.0-1
|
amd64 | test | fail | the archive's (reference arm) | 3.14 | — | 2026-08-26 21:02 |
2.8.0-1+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-08-27 02:17 |