Hi,

I've observed that a new build has been created in CBS https://cbs.centos.org/koji/buildinfo?buildID=49831 but it has epoch 1 while a previous one has epoch 2 https://cbs.centos.org/koji/buildinfo?buildID=40574 so still the old one is pulled.

Apparently epoch was decreased in https://git.centos.org/rpms/ceph/c/0ca9b1baa36c3e1184535f619cf82909616d1012?branch=c9s-sig-storage-ceph-quincy

Regards,

Alfredo

On Mon, Jul 10, 2023 at 4:11 PM Alfredo Moralejo Alonso <amoralej@redhat.com> wrote:

Hi,

After the update of liburing in centos stream 9, we are having issues to install ceph and qemu-kvm together:

# dnf install ceph qemu-kvm
Last metadata expiration check: 0:01:00 ago on Mon Jul 10 14:02:55 2023.
Error:
 Problem: cannot install both liburing-2.3-2.el9.x86_64 and liburing-0.7-7.el9.x86_64
  - package qemu-kvm-core-17:8.0.0-6.el9.x86_64 requires liburing.so.2()(64bit), but none of the providers can be installed
  - package qemu-kvm-core-17:8.0.0-6.el9.x86_64 requires liburing.so.2(LIBURING_2.0)(64bit), but none of the providers can be installed
  - package ceph-osd-2:17.2.3-2.el9s.x86_64 requires liburing.so.1()(64bit), but none of the providers can be installed
  - package ceph-osd-2:17.2.3-2.el9s.x86_64 requires liburing.so.1(LIBURING_0.1)(64bit), but none of the providers can be installed
  - package qemu-kvm-17:8.0.0-6.el9.x86_64 requires qemu-kvm-core = 17:8.0.0-6.el9, but none of the providers can be installed
  - package ceph-2:17.2.3-2.el9s.x86_64 requires ceph-osd = 2:17.2.3-2.el9s, but none of the providers can be installed
  - cannot install the best candidate for the job

Any help from storage sig will be appreciated.

Best regards,

Alfredo

_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
https://lists.centos.org/mailman/listinfo/centos-devel