On 12/05/2024 11:36, László Böszörményi (GCS) wrote:
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: transition
Control: affects -1 + src:snappy
Hi RMs,
Upstream of snappy changed function signatures [1] breaking other
applications with the 1.2.0 release. I've added back the original
function signatures calling the new ones to restore the immediate
problem, to restore the ABI. But then this creates ambiguity in the
Compress method signatures [2] making (only) ceph FTBFS. While it can
be patched to avoid it, a proper transition should be done.
I've renamed back the library name which was done due to the C++11 ABI
change with g++ 5.0 back in 2015.
Why is there a libsnappy1v5 transitional package?
Also has upstream been contacted in order to do a proper SONAME bump? Otherwise
libsnappy1 will have to conflict with libsnappy1v5, and that will make both the
transition and upgrades harder, as they have to be done in lockstep. If they
broke the ABI, then a SONAME bump is in order, and that will make it easier for
us too.
Cheers,
Emilio
