8.2.15+dfsg-10 in the archive
built,
ours is 8.2.15+dfsg-10+py315.3,
waiting on gettext.
Nothing recorded is waiting on this one.
published,
8.2.15+dfsg-10+py315.3,
as work request 1404726.
Sent before this one:
8.2.15+dfsg-5+py315.1, 8.2.15+dfsg-10+py315.1, 8.2.15+dfsg-10+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 |
| 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 |
|---|---|---|---|---|---|---|---|
8.2.15+dfsg-10+py315.3
|
arm64 | build | pass | unknown | not read yet | — | 2026-10-01 15:16 |
8.2.15+dfsg-10+py315.3
|
amd64 | build | pass | unknown | not read yet | — | 2026-10-01 15:06 |
8.2.15+dfsg-10+py315.3
|
all | build | pass | unknown | not read yet | — | 2026-10-01 14:55 |
8.2.15+dfsg-10+py315.2
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-24 23:31 |
8.2.15+dfsg-10+py315.2
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-24 23:20 |
8.2.15+dfsg-10+py315.2
|
all | build | pass | unknown | not read yet | — | 2026-09-24 23:11 |
8.2.15+dfsg-10+py315.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-09-01 11:11 |
8.2.15+dfsg-10+py315.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-09-01 11:01 |
8.2.15+dfsg-10+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-09-01 10:51 |
8.2.15+dfsg-5+py315.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-08-24 04:25 |