yum update
Last metadata expiration check: 0:00:11 ago on Tue Nov 14 08:20:06 2023.
Error:
Problem 1: package openldap-servers-2.6.2-2.el9.x86_64 requires openldap(x86-64) = 2.6.2, but none of the providers can be installed
cannot install both openldap-2.6.3-1.el9.x86_64 and openldap-2.6.2-3.el9.x86_64
cannot install the best update candidate for package openldap-servers-2.6.2-2.el9.x86_64
cannot install the best update candidate for package openldap-2.6.2-3.el9.x86_64
Problem 2: problem with installed package openldap-servers-2.6.2-2.el9.x86_64
package openldap-servers-2.6.2-2.el9.x86_64 requires openldap(x86-64) = 2.6.2, but none of the providers can be installed
cannot install both openldap-2.6.3-1.el9.x86_64 and openldap-2.6.2-3.el9.x86_64
package openldap-clients-2.6.3-1.el9.x86_64 requires openldap(x86-64) = 2.6.3-1.el9, but none of the providers can be installed
cannot install the best update candidate for package openldap-clients-2.6.2-3.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)
The openldap-servers is deprecated in RHEL. EPEL has the 2.6.2-2, built 2022-09.
That is, for el9_0 or el9_1. Alma 9.2’s openldap 2.6.2-3 packages were built 2022-10, probably for el9_1.
The 2.6.3-1 packages are for el9_3 and you have to wait until EPEL rebuilds the openldap-servers for el9_3.
EPEL is a collection of packages maintained by a number of maintainers. Each will update as these maintainers manage to juggle work, home and EPEL. You can always try enabling epel-testing if you’re desperate.
They could have at least waited for all packages to have the same version on production. I’m having the same issue and it is like dealing with a cyclical dependance. You cannot uninstall the default package of openldap “openldap.x86_64”, and you can’t install openldap-servers or clients because the system has a newer version of openldap.
I need to do an installation at a customer, so this does not look great !
Red Hat is one and released all packages of RHEL 9.3 at once.
AlmaLinux project is one and released all packages of AlmaLinux 9.3 at once, but not at same time with RHEL 9.3.
Other distros (that closely resemble RHEL) did/do the same.
EPEL is not one. It is many. Should all of them wait until all of them get their “for 9.3” builds complete and tested before release? If they would, then all of EPEL could still be “for 9.2”, and users of all distros that are already 9.3 content could have plenty of issues with EPEL.
Formally, a third party cannot start to build “for 9.3” before there is a 9.3 to build for and test in. Therefore, third parties cannot quite release at same time as RHEL 9.3 does.
According to EPEL the openldap-servers-2.6.3-1.el9 was pushed to stable 5 hours ago (and was in testing for a week before that).
I had to refresh metadata (dnf --disablerepo=* clean all) before dnf saw it in ‘epel’.
When RHEL 8 had been released and openldap-servers was no longer in it, I had to ponder how to proceed with the openldap server that I had on CentOS 6. I did end up installing 389-DS into CentOS Linux 8. The data did migrate relatively easily (slapcat, sed & small edits, import).
