This issue is purely informational, you do not need to take any action. Thank you for your work maintaining gdal in EPEL 10. Red Hat considers this package important enough to promote it to official RHEL. It will be part of RHEL 10.1. Please do not update gdal in EPEL 10 so the RHEL version can have a higher version and release. When RHEL 10.1 is released, EPEL automation will remove gdal from EPEL 10 and close this bug.
Based on the content in CentOS 10, it looks like only these subpackages from the build are being added to RHEL 10.1: * gdal * gdal-devel * gdal-libs Other subpackages from the EPEL build are not currently on track to be added, and will effectively disappear when the EPEL package is retired. * gdal-java * gdal-javadoc * gdal-python-tools * python3-gdal If these packages are important, please follow the instructions in the EPEL docs to either request those subpackages be included in RHEL, or create a gdal-epel package to provide the missing subpackages. https://docs.fedoraproject.org/en-US/epel/epel-policy-missing-sub-packages/
FWIW I thought I was hitting this problem with python3-gdal on a mailman server, but: dnf rm --noautoremove gdal-libs libspatialite libgeotiff ...solved it. YMMV.
gdal is now in RHEL10 as of RHEL 10.1. It has been retired from EPEL10 and EPEL10.1. It will take a day or two before it is out of the epel repositories and mirrors.
I would just like to remind you that the CentOS GDAL package is severely broken and it is missing most of its drivers. I did report it a few months ago - when it first appeared - and I was told to use the EPEL package. I see that now the EPEL package has been retired. I am the maintainer of the GDAL bindings for JavaScript, CentOS Stream 10 has been part of my testing setup for years. I will temporally disable testing on CentOS until a solution is found.
I'm the main GDAL developer and I just tried the GDAL package in AlmaLinux 10.1 and to my horror I've discovered it has hardly any driver enabled , not even TIFF. It makes it totally unusable for any practical reason. I don't have access to RHEL itself but seeing in the .src.rpm of AlmaLinux the following, I totally understand why it happened %cmake \ -DCMAKE_INSTALL_INCLUDEDIR=include/gdal \ %if %{with java} -DGDAL_JAVA_INSTALL_DIR=%{_jnidir}/%{name} \ -DGDAL_JAVA_JNI_INSTALL_DIR=%{_jnidir}/%{name} \ %endif %if ! 0%{?fedora} -DGDAL_BUILD_OPTIONAL_DRIVERS=OFF \ -DOGR_BUILD_OPTIONAL_DRIVERS=OFF \ -DGDAL_USE_JPEG=ON \ -DGDAL_USE_JPEG_INTERNAL=OFF \ -DGDAL_USE_GOOGLETEST=OFF \ -DGDAL_USE_LERC=OFF \ -DGDAL_USE_LERC_INTERNAL=OFF \ -DGDAL_USE_GEOTIFF=OFF \ -DGDAL_USE_GEOTIFF_INTERNAL=OFF \ -DBUILD_PYTHON_BINDINGS=OFF \ -DBUILD_TESTING=OFF \ %endif -DGDAL_USE_JPEG12_INTERNAL=OFF \ -DENABLE_DEFLATE64=OFF %cmake_build Note the "%if ! 0%{?fedora}" test that sets -DGDAL_BUILD_OPTIONAL_DRIVERS=OFF -DOGR_BUILD_OPTIONAL_DRIVERS=OFF and also -DGDAL_USE_GEOTIFF=OFF -DGDAL_USE_GEOTIFF_INTERNAL=OFF. All those settings shouldn't be set, unless people know what they are doing and have good reasons to create minimal builds.