Shortcuts

/
focus the search box
Escape
leave the search, or close a menu or this
r
cycle the refresh interval
t
cycle the theme
?
this list

← All states

Where it stands

built, ours is 1.1.1-5+py315.2.

Nothing recorded is waiting on this one.

What was sent

published, 1.1.1-5+py315.2, as work request 1237875.

Sent before this one: 1.1.1-5+py315.1. A version that was sent is spent, whatever came of it.

What is known

QuestionAnswerSaid byAs 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-charset-normalizer 3.4.7-2: we publish 3.4.7-2+py315.1
python3-h5py-serial 3.16.0-5+py315.1: we publish 3.16.0-6+py315.1
python3-skbio 0.7.3-1: not in our suite at all
python3-statsmodels-lib 0.14.6+dfsg-3: we publish 0.14.6+dfsg-3+py315.3
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.
ModuleNotFoundError: No module named 'skbio.metadata._intersection'
could not import skbio.metadata._intersection
deps/11 not dated
does Debian's own test suite pass? neutral
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

Runs

VersionArchKindResultBinariesInterpretersClosureFinished
1.1.1-5+py315.2 all build pass unknown not read yet — 2026-09-06 21:41
1.1.1-5+py315.1 all build fail unknown not read yet — 2026-08-19 08:27