5.1.3-1 in the archive
built,
ours is 5.1.3-1+py315.1,
waiting on furo, hatchling, python-aiosmtpd, python-hypothesis, python-pytest-asyncio, python-trustme, sphinx-autodoc-typehints, sphinx-copybutton, uvloop.
Nothing recorded is waiting on this one.
published,
5.1.3-1+py315.1,
as work request 1263661.
Sent before this one:
5.1.2-1+py315.1, 5.1.2-1+py315.2.
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-uvloop 0.22.1+ds1-3+py315.1: we publish 0.22.1+ds1-4+py315.1 |
deps/11 | not dated |
| Which known interpreter change does this failure show? |
tests-failed
the test suite failed, cause not narrowed. The tests failed under the new interpreter and nothing here recognises why. =================================== FAILURES =================================== |
deps/11 | not dated |
| do Debian's own tests pass? |
archive tests fail
Debian's own tests for this package fail in unstable, so this failure is not the new interpreter's doing. debci answers about the source rather than about the version we rebuilt, which is why the date its run happened is shown. arm64, last run 2026-03-24 |
ci.debian.net | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
5.1.3-1+py315.1
|
amd64 | test | pass | rebuilt | named none | — | 2026-09-13 15:58 |
5.1.3-1
|
amd64 | test | pass | the archive's (reference arm) | named none | — | 2026-09-13 15:13 |
5.1.3-1+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-09-13 15:55 |
5.1.2-1+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-08-28 00:13 |
5.1.2-1
|
amd64 | test | pass | the archive's (reference arm) | named none | — | 2026-08-27 03:28 |