3.0.2-2 in the archive
built,
ours is 3.0.2-3+py315.3,
waiting on dh-doc-privacy, poetry-core, python-async-timeout, python-bumble, python-pytest-asyncio, python-pytest-cov, python-typing-extensions, sphinx-rtd-theme.
ahead of the archive (built from a source sid does not have)
Nothing recorded is waiting on this one.
published,
3.0.2-3+py315.2,
as work request 1188980,
which ended in work request 1188987.
Which turned out to be tests-aborted: the tests were stopped: work request 1188987.
Sent before this one:
3.0.2-1+py315.1, 3.0.2-2+py315.1, 3.0.2-2+py315.2, 3.0.2-2+py315.3, 3.0.2-2+py315.4, 3.0.2-2+py315.5.
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. E ModuleNotFoundError: No module named 'typing_extensions' could not import typing_extensions |
deps/11 | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
3.0.2-3+py315.3
|
amd64 | test | pass | rebuilt | 3.14, 3.15 | suite-not-recorded | 2026-09-02 10:06 |
3.0.2-3+py315.3
|
all | build | pass | unknown | not read yet | — | 2026-09-02 10:04 |
3.0.2-2+py315.5
|
all | build | fail | unknown | not read yet | — | 2026-08-31 07:40 |
3.0.2-2
|
amd64 | test | fail | the archive's (reference arm) | 3.14 | — | 2026-08-27 09:23 |