Description of problem: The update to corosynclib-3.1.8-2 is missing the corresponding update to corosync-3.1.8 Version-Release number of selected component (if applicable): [root@ma-vcxaq ~]# dnf list corosync Last metadata expiration check: 2:26:18 ago on Fri 22 Nov 2024 01:59:49 PM CET. Available Packages corosync.x86_64 3.1.7-0.1.el9.1 epel [root@ma-vcxaq ~]# dnf install corosync Last metadata expiration check: 2:27:03 ago on Fri 22 Nov 2024 01:59:49 PM CET. Error: Problem: conflicting requests - nothing provides corosynclib(x86-64) = 3.1.7 needed by corosync-3.1.7-0.1.el9.1.x86_64 from epel (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) [root@ma-vcxaq ~]# rpm -q epel-release epel-release-9-5.al9.cern.noarch [root@ma-vcxaq ~]# cat /etc/*release* AlmaLinux release 9.5 (Teal Serval) NAME="AlmaLinux" VERSION="9.5 (Teal Serval)" ID="almalinux" ID_LIKE="rhel centos fedora" VERSION_ID="9.5" PLATFORM_ID="platform:el9" PRETTY_NAME="AlmaLinux 9.5 (Teal Serval)" ANSI_COLOR="0;34" LOGO="fedora-logo-icon" CPE_NAME="cpe:/o:almalinux:almalinux:9::baseos" HOME_URL="https://almalinux.org/" DOCUMENTATION_URL="https://wiki.almalinux.org/" BUG_REPORT_URL="https://bugs.almalinux.org/" ALMALINUX_MANTISBT_PROJECT="AlmaLinux-9" ALMALINUX_MANTISBT_PROJECT_VERSION="9.5" REDHAT_SUPPORT_PRODUCT="AlmaLinux" REDHAT_SUPPORT_PRODUCT_VERSION="9.5" SUPPORT_END=2032-06-01 AlmaLinux release 9.5 (Teal Serval) AlmaLinux release 9.5 (Teal Serval) cpe:/o:almalinux:almalinux:9::baseos [root@ma-vcxaq ~]# How reproducible: Just try to install corosync with "dnf install corosync" Steps to Reproduce: 1. Install epel-release-9-5 2. dnf install corosync 3. Actual results: [root@ma-vcxaq ~]# dnf install corosync Last metadata expiration check: 2:27:03 ago on Fri 22 Nov 2024 01:59:49 PM CET. Error: Problem: conflicting requests - nothing provides corosynclib(x86-64) = 3.1.7 needed by corosync-3.1.7-0.1.el9.1.x86_64 from epel (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) [root@ma-vcxaq ~]# Expected results: Additional info:
This is known problem but sadly unable to fix it without updated libqb-epel (I've tried to fix this problem 4 months ago and build failed because libqb from appstream is version libqb.so.100.3.2 and epel libqb.so points to libqb.so.100.3.0). We've tried to contact libqb-epel maintainer sadly without success. But you can try to open libqb-epel bz, maybe it helps. Once libqb-epel gets updated I will build corosync-epel.
Thanks. We have created a libqb issue related to this one: https://bugzilla.redhat.com/show_bug.cgi?id=2328642
I've got maintainer permissions for libqb-epel and kronosnet-epel - updated libqb-epel and kronosnet-epel for epel9 are now in testing so I should be able to build updated corosync once they get into epel stable so I expect updated corosync-epel should be installable in about 2 weeks. Same applies for epel8.
FEDORA-EPEL-2025-cdb8b1d984 (Sync corosync package version with c9s) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-cdb8b1d984
FEDORA-EPEL-2025-cdb8b1d984 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-cdb8b1d984 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-cdb8b1d984 (corosync-epel-3.1.8-0.1.el9.1) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.