On Sun, 16 Mar 2025 at 14:28:52 +0000, Luca Boccassi wrote:
I'll try to look into fixing python3-zstandard, it's unfortunate that the zstd transition was started to late
It's a bit of a weird transition, because upgrading a library to a new micro version with no new SONAME and no API/ABI breaks would normally be treated as a completely routine thing that doesn't need transitions or coordination, but python3-zstandard seems to be unusually tightly-coupled to an exact version of libzstd.
smcv
