aetos

3.0.0-2 in the archive

bugs: 2026-10-14 18:45 UTC
debci: 2026-10-14 04:49 UTC
graph: 2026-10-14 04:25 UTC
scan: 2026-10-14 19:00 UTC
states: 2026-10-14 19:18 UTC
sync: 2026-10-14 19:18 UTC
transition: 2026-10-14 04:49 UTC

Where it stands

build failed, ours is 3.0.0-2+py315.1, waiting on paste, pastedeploy, python-keystonemiddleware, python-observabilityclient, python-openstackdocstheme, python-oslo.config, python-oslo.i18n, python-oslo.log, python-oslo.middleware, python-oslo.policy, python-oslo.utils, python-oslotest, python-pbr, python-pecan, python-reno, python-stestr, python-testtools, python-wsme, sphinxcontrib-pecanwsme, subunit, webtest.

Nothing recorded is waiting on this one.

What was sent

Which turned out to be build-failed: the workflow ended: build-failed, work request 1443571.

Sent before this one: 2.0.0-1+py315.1, 3.0.0~rc1-2+py315.1, 3.0.0-1+py315.1. A version that was sent is spent, whatever came of it.

What is known

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-bcrypt 5.0.0-7: we publish 5.0.0-6+py315.2	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 'bcrypt._bcrypt' could not import bcrypt._bcrypt	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

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-bcrypt 5.0.0-7: we publish 5.0.0-6+py315.2

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 'bcrypt._bcrypt'
could not import bcrypt._bcrypt

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

Runs

Version	Arch	Kind	Result	Binaries	Interpreters	Closure	Finished
`3.0.0-2+py315.1`	all	build	fail	unknown	not read yet	—	2026-10-11 16:54
`3.0.0-1+py315.1`	all	build	pass	unknown	not read yet	—	2026-09-30 22:07
`3.0.0~rc1-2+py315.1`	all	build	pass	unknown	not read yet	—	2026-09-20 19:19
`2.0.0-1+py315.1`	all	build	pass	unknown	not read yet	—	2026-09-03 15:36

Version

Arch

Kind

Result

Binaries

Interpreters

Closure

Finished

3.0.0-2+py315.1

all

build

fail

unknown

not read yet

—

2026-10-11 16:54

3.0.0-1+py315.1

all

build

pass

unknown

not read yet

—

2026-09-30 22:07

3.0.0~rc1-2+py315.1

all

build

pass

unknown

not read yet

—

2026-09-20 19:19

2.0.0-1+py315.1

all

build

pass

unknown

not read yet

—

2026-09-03 15:36