6.2.0+ds-10 in the archive
built,
ours is 6.2.0+ds-10+py315.2.
Nothing recorded is waiting on this one.
published,
6.2.0+ds-10+py315.2,
as work request 1346041.
Sent before this one:
6.2.0+ds-9+py315.1, 6.2.0+ds-10+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 |
| 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 |
| does the archive build this version? |
archive ftbfs
Debian's own rebuild of the version the archive carries fails too, so this failure is not the new interpreter's doing. It still blocks the transition: nobody can rebuild it until that is fixed. amd64 |
tests.reproducible-builds.org | 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 |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
6.2.0+ds-10+py315.2
|
all | build | pass | unknown | not read yet | — | 2026-09-24 23:37 |
6.2.0+ds-10+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-09-21 19:24 |
6.2.0+ds-9+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-08-25 07:30 |