Re: pydantic/pydantic-core mismatch [resulted in old synapse in 2025Q4]

[Greg Troxel <gdt%lexort.com@localhost>]

Greg Troxel <gdt%lexort.com@localhost> writes:

> Upgrading synapse to 1.143.0 (on 9/2025Q3) results in an exception at
> start, which is reproducible (NetBSD 10, pkgsrc HEAD):

> The upstream bug:
>
>   https://github.com/pydantic/pydantic/issues/12189

This was too much of a mess for me to deal with during
pre-freeze/freeze, so I left it, as my own systems have up-to-date
synapse and I was merely trying to be helpful to theoretical other
people that are using the package.

I never heard from anyone about the substance of this problem, which
seems to stem from mismatching versions in updates from ~June.  (It
could be that this latent bug was not exposed until more recent
synapse.)

Adam's recent update to pydantic/pydantic-core did bring both to a
version pair that upstream considered ok, but kept the incorrect
relaxation of the exact dependency requirement.  I just fixed that
(dropping the == to >= patch for pyproject.toml), and added a comment
explaining the situation for these two packages.

With HEAD versions of pydantic and pydantic-core, the updated version of
matrix-synapse, just now committed, builds ok.