Bug 2362723
| Summary: | Notice: proj will be automatically retired from EPEL 9 when RHEL 9.7 is released | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | rhel-process-autobot <rhel-process-autobot> |
| Component: | proj | Assignee: | markusN <neteler> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel9 | CC: | devrim, manisandro, neteler, romain.geissler, steve.traylen, tdawson, wonczak |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-11-20 18:55:45 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1998160 | ||
|
Description
rhel-process-autobot
2025-04-28 15:34:40 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. 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. 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. Hi, epel-proj package needs to go. 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. 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. |