I had a look at this bug report.
It seems the error comes from pydantic (pydantic code called by other
parts of pydantic); it still occurs with the recent upload of pydantic
2.4.2.
I tried doing a package for the newer upstream release (2.8.2) with a
simple gbp import-orig --uscan (and refreshing the patches), but that
one fails to build too, seemingly due to a too old pydantic-core.
So I tried doing a package for the newer upstream release of
pydantic-core (2.20.1) with the same procedure, but that one requires a
Rust module (jiter) that doesn't seem to be packaged yet.
I'm giving up on that for today, but if anyone is interested, here's the
brain dump :-)
Roland.
