Bug 2166609 - [EPEL 7] [gdal] gdal-libs 1.11.4-4 lost support for OpenJPEG
Summary: [EPEL 7] [gdal] gdal-libs 1.11.4-4 lost support for OpenJPEG
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: gdal
Version: epel7
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: markusN
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-02 10:22 UTC by Laurențiu Nicola
Modified: 2024-07-09 15:40 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-07-09 15:40:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Laurențiu Nicola 2023-02-02 10:22:39 UTC
Description of problem:
I can't test on a clean install because 1.11.4-3 is gone, but I still have an old container around:

```
[root@a24f3dcd52a9 /]# /usr/bin/gdalinfo --formats | grep JPEG
  JPEG (rwv): JPEG JFIF
  JP2OpenJPEG (rwv): JPEG-2000 driver based on OpenJPEG library
  JPEG2000 (rwv): JPEG-2000 part 1 (ISO/IEC 15444-1)
  JPEGLS (rwv): JPEGLS
[root@a24f3dcd52a9 /]# yum -y update gdal
[snip]
[root@a24f3dcd52a9 /]# /usr/bin/gdalinfo --formats | grep JPEG
  JPEG (rwv): JPEG JFIF
  JPEG2000 (rwv): JPEG-2000 part 1 (ISO/IEC 15444-1)
  JPEGLS (rwv): JPEGLS
```

Version-Release number of selected component (if applicable):
gdal-libs-1.11.4-4.el7

How reproducible:
Always

Steps to Reproduce:
1. install `gdal`
2. run `gdalinfo --formats | grep JPEG`
3. check whether `JP2OpenJPEG` is present

Actual results:
No `JP2OpenJPEG`.

Expected results:
`JP2OpenJPEG`.

Additional info:
`gdal-libs` still pulls in `openjpeg-libs` as a dependency and the `1.11.4-4` changelog only mentions an `armadillo` rebuild. I believe this was an issue during the rebuild.

Comment 1 markusN 2023-02-03 06:45:51 UTC
The last working built which I see it this one:

https://koji.fedoraproject.org/koji/buildinfo?buildID=1974442

Could you give it a try?

Comment 2 Laurențiu Nicola 2023-02-03 06:53:32 UTC
No, it doesn't appear to work:

[root@e758e66def44 /]# yum install -y -q gdal     
warning: /var/cache/yum/x86_64/7/epel/packages/CharLS-1.0-5.el7.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 352c64e5: NOKEY
Public key for CharLS-1.0-5.el7.x86_64.rpm is not installed
Importing GPG key 0x352C64E5:
 Userid     : "Fedora EPEL (7) <epel>"
 Fingerprint: 91e9 7d7c 4a5e 96f1 7f3e 888f 6a2f aea2 352c 64e5
 Package    : epel-release-7-11.noarch (@extras)
 From       : /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
[root@e758e66def44 /]# curl -LO https://kojipkgs.fedoraproject.org//packages/gdal/1.11.4/4.el7/x86_64/gdal-libs-1.11.4-4.el7.x86_64.rpm
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 4467k  100 4467k    0     0  1368k      0  0:00:03  0:00:03 --:--:-- 1368k
[root@e758e66def44 /]# curl -LO https://kojipkgs.fedoraproject.org//packages/gdal/1.11.4/4.el7/x86_64/gdal-1.11.4-4.el7.x86_64.rpm
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  273k  100  273k    0     0   234k      0  0:00:01  0:00:01 --:--:--  235k
[root@e758e66def44 /]# rpm -Uvh --force gdal-1.11.4-4.el7.x86_64.rpm gdal-libs-1.11.4-4.el7.x86_64.rpm 
Preparing...                          ################################# [100%]
Updating / installing...
   1:gdal-libs-1.11.4-4.el7           ################################# [ 50%]
   2:gdal-1.11.4-4.el7                ################################# [100%]
[root@e758e66def44 /]# gdalinfo --formats | grep JPEG
  JPEG (rwv): JPEG JFIF
  JPEG2000 (rwv): JPEG-2000 part 1 (ISO/IEC 15444-1)
  JPEGLS (rwv): JPEGLS

Comment 3 Laurențiu Nicola 2023-02-03 06:58:25 UTC
Take a look at https://kojipkgs.fedoraproject.org/packages/gdal/1.11.4/4.el7/data/logs/x86_64/build.log and https://kojipkgs.fedoraproject.org/packages/gdal/1.11.4/3.el7/data/logs/x86_64/build.log.

checking openjpeg-2.0/openjpeg.h usability... no
checking openjpeg-2.0/openjpeg.h presence... no
checking for openjpeg-2.0/openjpeg.h... no
checking openjpeg-2.1/openjpeg.h usability... no
checking openjpeg-2.1/openjpeg.h presence... no
checking for openjpeg-2.1/openjpeg.h... no
[snip]
  OpenJPEG support:          no

vs.

checking openjpeg-2.0/openjpeg.h usability... no
checking openjpeg-2.0/openjpeg.h presence... no
checking for openjpeg-2.0/openjpeg.h... no
checking openjpeg-2.1/openjpeg.h usability... yes
checking openjpeg-2.1/openjpeg.h presence... yes
checking for openjpeg-2.1/openjpeg.h... yes
[snip]
  OpenJPEG support:          yes

Comment 4 Laurențiu Nicola 2023-02-03 07:00:38 UTC
Ah, that's because OpenJPEG moved from 2.1.0-7.el7 to 2.3.1-3.el7_7 in the meanwhile. I assume GDAL 1.11.4 doesn't support the latter.

Comment 5 markusN 2023-02-03 17:44:40 UTC
For a new test, I have triggered a new GDAL 1.11.4 (scratch) build:

https://koji.fedoraproject.org/koji/taskinfo?taskID=97053326

which compiled fine. Would you mind to try this one?

Comment 6 Laurențiu Nicola 2023-02-03 18:30:24 UTC
It's not going to work. If you look at the build log, you'll see that the configure step says that OpenJPEG is not enabled.

As I mentioned above, this is almost certainly caused by bumping that from 2.1.0 to 2.3.1. Only downgrading OpenJPEG or patching GDAL can fix this.

Comment 7 markusN 2023-02-04 11:08:47 UTC
To be honest: GDAL 1.11.4 is rather old and from 2016 (https://trac.osgeo.org/gdal/wiki/Release/1.11.4-News).

Personally, I am not able to invest time into patching this old GDAL version for more modern JPEG support.
At least, I did an analysis:

Needed will be
- backport of https://trac.osgeo.org/gdal/ticket/7074
  - https://github.com/OSGeo/gdal/commit/3e762d9c942a649851f951ffd03eb482e38ac8db

Perhaps a volunteer is willing to take over?

Comment 9 Troy Dawson 2024-07-09 15:40:40 UTC
EPEL 7 entered end-of-life (EOL) status on 2024-06-30.  EPEL 7 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.


Note You need to log in before you can comment on or make changes to this bug.