1.4.0-2 in the archive
build failed,
ours is 1.4.0-2+py315.2.
Nothing recorded is waiting on this one.
aborted,
1.4.0-2+py315.2,
as work request 1346208,
which ended in work request 1346210.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1346210.
Sent before this one:
1.4.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-psutil 7.1.0-1.1+py315.2: we publish 7.2.2-1+py315.1 |
deps/11 | not dated |
| does Debian's own test suite pass? |
neutral
Debian runs no autopkgtest for this, so we have no independent baseline: nothing here distinguishes a failure this interpreter caused from one the package always had |
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 #1149373 heudiconv: FTBFS against python 3.15rc2 (pydicom imports deprecated collections.abc.ByteString) |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
1.4.0-2+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-09-25 00:06 |
1.4.0-2
|
amd64 | test | pass | archive | 3.14, 3.15 | — | 2026-09-24 15:25 |
1.4.0-2+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-09-24 18:14 |