DevHeads.net

openjpeg-2.2.0

Hi

openjpeg-2.2.0 was just release, carrying a large number of security
fixes. I'd also like to update it for F25 and F26, since it is ABI and
API compatible with 2.1.x, there is however the problem that openjpeg2
installs its headers under /usr/include/openjpeg-$major.$minor, so this
would mean that the location of headers changes, potentially leading to
compilation failures in the unlikely event users have hardcoded the path
to said headers (instead of using the pkgconfig file). I'd say however
that this risk is worth the update.

Any objections to updating?

Thanks
Sandro

Comments

Re: openjpeg-2.2.0

By Rex Dieter at 08/10/2017 - 10:24

No objection, it should be fine for any app correctly using pkg-config
and/or cmake

-- Rex

Re: openjpeg-2.2.0

By Richard Shaw at 08/10/2017 - 10:41

You can check the api compliance with abi-compliance-checker first to be
sure...

$ abi-compliance-checker -L openjpeg -dump -vnum <old_version> -dump
<old_rpm>
$ abi-compliance-checker -L openjpeg -dump -vnum <new_version> -dump
<new_rpm>
$ abi-compliance-checker -L openjpeg -old <path/to/old/dump> -new
<path/to/new/dump>

I wrote that mostly from memory so definitely double check my work...

Thanks,
Richard

Re: openjpeg-2.2.0

By Richard Shaw at 08/10/2017 - 10:42

Thanks,
Richard

Re: openjpeg-2.2.0

By Sandro Mani at 08/10/2017 - 12:18

On 10.08.2017 17:42, Richard Shaw wrote:
Ok moving ahead and updating.

Thanks
Sandro

[1] <a href="https://github.com/uclouvain/openjpeg/blob/v2.2.0/NEWS.md" title="https://github.com/uclouvain/openjpeg/blob/v2.2.0/NEWS.md">https://github.com/uclouvain/openjpeg/blob/v2.2.0/NEWS.md</a>

Re: openjpeg-2.2.0

By Richard Hughes at 08/10/2017 - 10:37

On 10 August 2017 at 16:24, Rex Dieter < ... at math dot unl.edu> wrote:
Agreed; if an app breaks because it hardcoded the include path then it
should just have been using pkg-config.

Richard.

Re: openjpeg-2.2.0

By Matthew Miller at 08/10/2017 - 09:01

On Thu, Aug 10, 2017 at 10:55:07AM +0200, Sandro Mani wrote:
If it's _really_ API compatible, is it possible to include a symlink
for compatibility (in f26 and f25 packages, not for rawhide).