On 09/17/2015 10:28 AM, Sandro Mani wrote:
> - Nothing in Fedora seems to require libfreeimageplus, so just build
> 3.17 in rawhide and F23 and have the libfreeimageplus ABI break silently
> sneak in. Probably shouldn't even mention this option.
If nothing depends on it, just go with what's easies
On 17.09.2015 10:46, Florian Weimer wrote:
On 09/17/2015 10:28 AM, Sandro Mani wrote:
- abi_compliance_checker reports that compatibility was not broken
between libfreeimage of 3.10 and 3.17. However, in libfreeimageplus,
various function signatures have changed due to switching from WORD (ak
On 09/17/2015 10:28 AM, Sandro Mani wrote:
> - abi_compliance_checker reports that compatibility was not broken
> between libfreeimage of 3.10 and 3.17. However, in libfreeimageplus,
> various function signatures have changed due to switching from WORD (aka
> unsigned short) to unsigned for variou
Hello
I'm looking at updating freeimage from 3.10 to 3.17, also to resolve
CVE-2015-0852, and I'm wondering how to deal with the following situation:
- The package ships two libraries, libfreeimage (C API) and
libfreeimageplus (C++ wrapper)
- abi_compliance_checker reports that compatibility
