On Sat, May 09, 2026 at 12:46:24PM +0200, Santiago Vila wrote:
This problem fixed by itself without requiring any change in qcelemental.
So I did a debbisect and this was the outcome:
bisection finished successfully
last bad timestamp: 20260505T142927Z
first good timestamp: 20260506T023405Z
the following packages differ between the last bad and first good timestamp:
python3-pydantic 2.12.5-2 -> 2.13.3-1
python3-pydantic-core 2.41.5-5 -> 2.46.3-1
I'm choosing python3-pydantic because it's in debian/control as an
explicit build-dependency.
This makes sense, because the failure mentioned pydantic.v1 and was for
Python 3.14 only, and:
"This release contains the updated `pydantic.v1` namespace, matching
version 1.10.26 which includes support for Python 3.14."
--
Colin Watson (he/him) [[email protected]]