On 31/05/2023 09:30, lejeczek via CentOS-devel wrote:
Hi guys.
Just to let you know that with GlusterFS & latest qemu updates - on Centos 9 I'd image most will have these - there are conflicts which brake update:

-> $ dnf update

Error:
 Problem 1: package qemu-img-17:8.0.0-4.el9.x86_64 from appstream requires liburing.so.1()(64bit), but none of the providers can be installed
  - package qemu-img-17:8.0.0-4.el9.x86_64 from appstream requires liburing.so.1(LIBURING_0.1)(64bit), but none of the providers can be installed
  - package qemu-img-17:8.0.0-4.el9.x86_64 from appstream requires liburing.so.1(LIBURING_0.2)(64bit), but none of the providers can be installed
  - cannot install both liburing-0.7-7.el9.x86_64 from appstream and liburing-2.0-1.el9s.x86_64 from @System
  - cannot install the best update candidate for package qemu-img-17:8.0.0-2.el9.x86_64
  - cannot install the best update candidate for package liburing-2.0-1.el9s.x86_64
 Problem 2: package glusterfs-server-11.0-1.el9s.x86_64 from @System requires liburing.so.2()(64bit), but none of the providers can be installed
  - package glusterfs-server-11.0-1.el9s.x86_64 from @System requires liburing.so.2(LIBURING_2.0)(64bit), but none of the providers can be installed
  - cannot install both liburing-0.7-7.el9.x86_64 from appstream and liburing-2.0-1.el9s.x86_64 from @System
  - cannot install both liburing-0.7-7.el9.x86_64 from appstream and liburing-2.0-1.el9s.x86_64 from centos-gluster11
  - cannot install both liburing-0.7-7.el9.x86_64 from appstream and liburing-2.0-1.el9s.x86_64 from centos-gluster11-test
  - package qemu-kvm-core-17:8.0.0-4.el9.x86_64 from appstream requires liburing.so.1()(64bit), but none of the providers can be installed
  - package qemu-kvm-core-17:8.0.0-4.el9.x86_64 from appstream requires liburing.so.1(LIBURING_0.1)(64bit), but none of the providers can be installed
  - package qemu-kvm-core-17:8.0.0-4.el9.x86_64 from appstream requires liburing.so.1(LIBURING_0.2)(64bit), but none of the providers can be installed
  - cannot install the best update candidate for package qemu-kvm-core-17:8.0.0-2.el9.x86_64
  - cannot install the best update candidate for package glusterfs-server-11.0-1.el9s.x86_64
 Problem 3: problem with installed package liburing-2.0-1.el9s.x86_64
  - cannot install both liburing-0.7-7.el9.x86_64 from appstream and liburing-2.0-1.el9s.x86_64 from @System
  - cannot install both liburing-0.7-7.el9.x86_64 from appstream and liburing-2.0-1.el9s.x86_64 from centos-gluster11
  - cannot install both liburing-0.7-7.el9.x86_64 from appstream and liburing-2.0-1.el9s.x86_64 from centos-gluster11-test
  - package qemu-kvm-core-17:8.0.0-4.el9.x86_64 from appstream requires liburing.so.1()(64bit), but none of the providers can be installed
  - package qemu-kvm-core-17:8.0.0-4.el9.x86_64 from appstream requires liburing.so.1(LIBURING_0.1)(64bit), but none of the providers can be installed
  - package qemu-kvm-core-17:8.0.0-4.el9.x86_64 from appstream requires liburing.so.1(LIBURING_0.2)(64bit), but none of the providers can be installed
  - problem with installed package qemu-kvm-core-17:8.0.0-2.el9.x86_64
  - package qemu-kvm-core-17:8.0.0-2.el9.x86_64 from @System requires qemu-kvm-common = 17:8.0.0-2.el9, but none of the providers can be installed
  - package qemu-kvm-core-17:8.0.0-2.el9.x86_64 from appstream requires qemu-kvm-common = 17:8.0.0-2.el9, but none of the providers can be installed
  - cannot install both qemu-kvm-common-17:8.0.0-4.el9.x86_64 from appstream and qemu-kvm-common-17:8.0.0-2.el9.x86_64 from @System
  - cannot install both qemu-kvm-common-17:8.0.0-4.el9.x86_64 from appstream and qemu-kvm-common-17:8.0.0-2.el9.x86_64 from appstream
  - cannot install the best update candidate for package qemu-kvm-common-17:8.0.0-2.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)

many thanks, L.


Both GlusterFS releases 10 & 11.
This might spell "serious" trouble for some - quite a few groups pull those, eg. oVirt.