13.1.0-1 in the archive
built,
ours is 13.1.0-1+py315.1.
Nothing recorded is waiting on this one.
published,
13.1.0-1+py315.1,
as work request 1291709.
Sent before this one:
13.0.0-1+py315.1, 13.0.0-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? |
archive-dependency
Built against the archive's copy of a dependency we have rebuilt. The ordering has not reached it, so this is not the package's own fault. python3-pgmagick 0.7.6-2+b1: not in our suite at all |
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. ImportError: cannot import name '_pgmagick' from partially initialized module 'pgmagick' (most likely due to a circular import) (/usr/lib/python3/dist-packages/pgmagick/__init__.py) |
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 |
|---|---|---|---|---|---|---|---|
13.1.0-1+py315.1
|
amd64 | test | fail | rebuilt | named none | — | 2026-09-16 23:09 |
13.1.0-1
|
amd64 | test | fail | archive | 3.15 | — | 2026-09-16 21:21 |
13.1.0-1+py315.1
|
all | build | pass | unknown | not read yet | — | 2026-09-16 23:07 |
13.0.0-1
|
amd64 | test | fail | archive | 3.15 | — | 2026-09-06 15:18 |
13.0.0-1+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-09-06 21:20 |
13.0.0-1+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-08-25 00:32 |