Hi,
On 13.11.2014 13:55, Scott Kitterman wrote:
On Thursday, November 13, 2014 13:25:34 Sebastian Andrzej Siewior wrote:
We have depends on libclamav6 based on library functions / ABI. Now the
ABI remains unchanged but stops working. This was neither tested nor
expected.
The problem is that the API changed (subtly): CL_FLEVEL got increased.
I guess the simplest thing to do is to depend the whole clamav package
on the built version instead of versioned symbols like we now.
This check comes from check_flevel() and it is not exported so havp &
friends won't care about his.
Any comments?
The exported function is not check_flevel, but rather cl_retflevel,
which just returns CL_FLEVEL.
I don't have a better idea. We need to do something and that's the only
approach I can think of that avoids having to manually set a minimum version.
I think this is the wrong workaround.
The correct fix is to bump the minimal version requirement of
cl_retflevel to 0.98.5~rc1, which is the upstream version in which
CL_FLEVEL changed the last time.
We'll have to do that in the future every time CL_FLEVEL is increased.
It is important to note that c-icap-modules also uses cl_retflevel, even
though it doesn't use CL_FLEVEL directly. Thus it can't have a runtime
test failing with older libclamav.
Best regards,
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org