Bug 2362723 - Notice: proj will be automatically retired from EPEL 9 when RHEL 9.7 is released
Summary: Notice: proj will be automatically retired from EPEL 9 when RHEL 9.7 is released
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: proj
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: markusN
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: EPEL2RHEL
TreeView+ depends on / blocked
 
Reported: 2025-04-28 15:34 UTC by rhel-process-autobot
Modified: 2025-11-20 18:55 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-11-20 18:55:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description rhel-process-autobot 2025-04-28 15:34:40 UTC

Comment 1 rhel-process-autobot 2025-04-28 15:34:44 UTC
This issue is purely informational, you do not need to take any action. Thank you for your work maintaining proj in EPEL 9. Red Hat considers this package important enough to promote it to official RHEL. It will be part of RHEL 9.7. Please do not update proj in EPEL 9 so the RHEL version can have a higher version and release. When RHEL 9.7 is released, EPEL automation will remove proj from EPEL 9 and close this bug.

Comment 2 Dr. Stephan Wonczak 2025-07-23 13:12:54 UTC
Just from information:

One problem here:
The situation right now is that proj from EPEL-9 conflicts with RHEL-9 appstream. This prevents several packages from being updated:

[root@mycroft~]$ LANG=C dnf update
Last metadata expiration check: 0:23:36 ago on Wed Jul 23 14:45:33 2025.
Error: 
 Problem 1: package opencv-core-4.6.0-7.el9.x86_64 from @System requires libgdal.so.30()(64bit), but none of the providers can be installed
  - cannot install both gdal-libs-3.10.3-3.el9.x86_64 from appstream and gdal-libs-3.4.3-3.el9.x86_64 from @System
  - cannot install both gdal-libs-3.4.3-3.el9.x86_64 from epel and gdal-libs-3.10.3-3.el9.x86_64 from appstream
  - cannot install the best update candidate for package opencv-core-4.6.0-7.el9.x86_64
  - cannot install the best update candidate for package gdal-libs-3.4.3-3.el9.x86_64
 Problem 2: package libspatialite-5.0.1-17.el9.x86_64 from @System requires libproj.so.22()(64bit), but none of the providers can be installed
  - cannot install both proj-9.6.0-2.el9.x86_64 from appstream and proj-8.2.0-1.el9.x86_64 from @System
  - cannot install both proj-8.2.0-1.el9.x86_64 from epel and proj-9.6.0-2.el9.x86_64 from appstream
  - cannot install the best update candidate for package proj-8.2.0-1.el9.x86_64
  - cannot install the best update candidate for package libspatialite-5.0.1-17.el9.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

If you try to "force" the update to the @appstream version, quite a few dependent packages from EPEL are affected:


[root@mycroft~]$ LANG=C dnf update proj --best --allowerasing
Last metadata expiration check: 0:25:35 ago on Wed Jul 23 14:45:33 2025.
Dependencies resolved.
==================================================================================================================
 Package                        Architecture        Version                         Repository               Size
==================================================================================================================
Upgrading:
 gdal-libs                      x86_64              3.10.3-3.el9                    appstream               3.5 M
 proj                           x86_64              9.6.0-2.el9                     appstream               1.5 M
Installing dependencies:
 proj-data                      noarch              9.6.0-2.el9                     appstream               1.3 M
Removing dependent packages:
 OpenImageIO                    x86_64              2.4.17.0-2.el9                  @epel                   9.2 M
 OpenImageIO-devel              x86_64              2.4.17.0-2.el9                  @epel                   1.8 M
 OpenImageIO-iv                 x86_64              2.4.17.0-2.el9                  @epel                   341 k
 OpenImageIO-utils              x86_64              2.4.17.0-2.el9                  @epel                   2.0 M
 digikam                        x86_64              8.3.0-1.el9.next                @epel-next               63 M
 digikam-libs                   x86_64              8.3.0-1.el9.next                @epel-next               42 M
 libgeotiff                     x86_64              1.7.1-3.el9                     @epel                   357 k
 libspatialite                  x86_64              5.0.1-17.el9                    @epel                    16 M
 opencv                         x86_64              4.6.0-7.el9                     @epel                    10 M
 opencv-contrib                 x86_64              4.6.0-7.el9                     @epel                    12 M
 opencv-core                    x86_64              4.6.0-7.el9                     @epel                    25 M
 opencv-devel                   x86_64              4.6.0-7.el9                     @epel                   7.2 M

Transaction Summary
==================================================================================================================
Install   1 Package
Upgrade   2 Packages
Remove   12 Packages

These dependencies should be resolved together with dropping proj from EPEL.

Comment 3 Troy Dawson 2025-07-23 14:55:36 UTC
I just checked, and proj is not in RHEL 9.6, so this is not affecting RHEL users yet.
It is in CentOS Stream 9, and yes, that currently is a problem.

When RHEL 9.7 is released we will be removing proj from epel9.
At that point, affected epel packages will need to be rebuilt.

Comment 4 Steve Traylen 2025-11-20 08:50:38 UTC
Hi, 

epel-proj package needs to go.

Comment 5 Troy Dawson 2025-11-20 17:42:29 UTC
Working on it.
proj was released in RHEL 9.7
It seems tagging permissions changed since our last RHEL release and we can't untag our usual way.

Comment 6 Troy Dawson 2025-11-20 18:55:45 UTC
proj is now in RHEL9 as of RHEL 9.7.
It has been retired from EPEL9.
It will take a day or two before it is out of the epel9 repositories and mirrors.


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