0.46.0-2 in the archive
built,
ours is 0.46.0-2+py315.2,
waiting on dh-fortran, ecbuild, eckit, fckit, llvm-defaults.
Nothing recorded is waiting on this one.
published,
0.46.0-2+py315.2,
as work request 1250559.
Sent before this one:
0.46.0-2+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 |
| 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 |
| does the release team track this? |
dependency level 6
The release team's own tracker lists it, and their dependency level is how the transition is sequenced: a level cannot be read as done while anything below it is outstanding. Their question is what a package's binaries depend on, not what it ships, so their verdict and ours can disagree without either being wrong. amd64 unknown, arm64 unknown, armhf unknown, i386 unknown, loong64 unknown, ppc64el unknown, riscv64 unknown, s390x unknown not in testing, so sid only |
release.debian.org, from their ben tracker | 2026-09-16 04:49 UTC |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
0.46.0-2+py315.2
|
arm64 | build | pass | unknown | not read yet | — | 2026-09-10 18:29 |
0.46.0-2+py315.2
|
amd64 | build | pass | unknown | not read yet | — | 2026-09-10 18:27 |
0.46.0-2+py315.1
|
arm64 | build | fail | unknown | not read yet | — | 2026-08-22 19:47 |
0.46.0-2+py315.1
|
amd64 | build | fail | unknown | not read yet | — | 2026-08-22 19:44 |