2.5-1 in the archive
build failed,
ours is 2.5-1+py315.2.
Nothing recorded is waiting on this one.
aborted,
2.5-1+py315.2,
as work request 1347665,
which ended in work request 1347667.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1347667.
Sent before this one:
2.5-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 Debian's own test suite pass? |
not tested by debian
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 #1120194 staticsite: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.13 returned exit code 13 |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
2.5-1+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-09-25 03:55 |
2.5-1+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-08-25 06:44 |