0.10.1+dfsg-2 in the archive
build failed,
ours is 0.10.1+dfsg-2+py315.3.
Nothing recorded is waiting on this one.
published,
0.10.1+dfsg-2+py315.3,
as work request 1346828.
Sent before this one:
0.10.1+dfsg-2+py315.1, 0.10.1+dfsg-2+py315.2.
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 |
| Which known interpreter change does this failure show? |
module-not-importable
a dependency was not importable. Nothing here says the interpreter caused this. An import that failed usually means the testbed was assembled before the dependency had been rebuilt, which is ours to fix by running it again. raise ModuleNotFoundError(msg, name=modname) # NoQA: TRY301 could not import csb43 |
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 #1149339 python-csb43: FTBFS against python 3.15rc2 (sphinx fails to find the csb43 module) |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
0.10.1+dfsg-2+py315.3
|
all | build | fail | unknown | not read yet | — | 2026-09-25 02:42 |
0.10.1+dfsg-2+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-08-28 01:31 |
0.10.1+dfsg-2
|
amd64 | test | pass | the archive's (reference arm) | 3.14 | — | 2026-08-27 03:28 |