1.7.0+ds-2 in the archive, ships a compiled extension
build failed,
ours is 1.7.0+ds-2+py315.d.2.
left on 2026-09-18
Nothing recorded is waiting on this one.
aborted,
1.7.0+ds-2+py315.d.2,
as work request 1278342,
which ended in work request 1278344.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1278344.
Sent before this one:
1.7.0+ds-2+py315.d.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 |
| Is this filed in Debian? |
#1145080
Filed by this round, or adopted from the BTS by its usertag. |
the tracker's own record | 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 #1145080 (done) python-backports.zstd: FTBFS building against python 3.15 |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
1.7.0+ds-2+py315.d.2
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-15 13:34 |
1.7.0+ds-2+py315.d.2
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-15 13:36 |
1.7.0+ds-2
|
arm64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-13 15:13 |
1.7.0+ds-2
|
amd64 | test | fail | the archive's (reference arm) | named none | — | 2026-09-13 15:13 |
1.7.0+ds-2+py315.d.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-13 17:11 |
1.7.0+ds-2+py315.d.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-13 17:30 |