ccdproc

2.5.1-3 in the archive

Where it stands

built, ours is 2.5.1-3+py315.2.

Nothing recorded is waiting on this one.

published, 2.5.1-3+py315.2, as work request 1237644.

Sent before this one: 2.5.1-3+py315.1. 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-reproject 0.21.0-1: not in our suite at all python3-zopfli 0.4.3-1+py315.1: we publish 0.4.3-2+py315.1	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. [33mSKIPPED[0m [3] ccdproc/tests/run_for_memory_profile.py:3: could not import 'memory_profiler': No module named 'memory_profiler' could not import memory_profiler, reproject.adaptive.deforest	deps/11	not dated

Version	Arch	Kind	Result	Binaries	Interpreters	Closure	Finished
`2.5.1-3+py315.2`	amd64	test	pass	rebuilt	named none	—	2026-09-06 20:44
`2.5.1-3+py315.2`	all	build	pass	unknown	not read yet	—	2026-09-06 20:42
`2.5.1-3`	amd64	test	pass	the archive's (reference arm)	named none	—	2026-08-24 15:24
`2.5.1-3+py315.1`	all	build	fail	unknown	not read yet	—	2026-08-24 18:03