That’s a major misinterpretation of how it actually is in reality. Sorry just had to state that, obviously not the proper mailing list to discuss it on. Best regards Tobias > On 4 Aug 2023, at 09:25, Jens Galsgaard <jens@xxxxxxxxxxxxx> wrote: > > Your are right. > > Centos stream is alpha > Fedora is beta > RHEL is stable > > Alma/Rocky/Oracle are based on RHEL > > Venlig hilsen - Mit freundlichen Grüßen - Kind Regards, > Jens Galsgaard > > Gitservice.dk > Mob: +45 28864340 > > > -----Oprindelig meddelelse----- > Fra: Marc <Marc@xxxxxxxxxxxxxxxxx> > Sendt: Friday, 4 August 2023 09.04 > Til: Konstantin Shalygin <k0ste@xxxxxxxx>; dobrie2@xxxxxxx > Cc: ceph-users@xxxxxxx > Emne: Re: Ceph Quincy and liburing.so.2 on Rocky Linux 9 > > But Rocky Linux 9 is the continuation of what CentOS would have been on el9. Afaik is ceph being developed on elX distributions and not the 'trial' stream versions, not? > > >> >> In most cases the 'Alternative' distro like Alma or Rocky have >> outdated versions of packages, if we compared it with CentOS Stream 8 >> or CentOS Stream 9. For example is a golang package, on c8s is a 1.20 >> version on Alma still 1.19 >> >> You can try to use c8s/c9s or try to contribute to your distro to >> resolve dependency issues >> >> >>> >>> I've been digging and I can't see that this has come up anywhere. >>> >>> I'm trying to update a client from Pacific 17.2.3-2 to 17.2.6-4 and >> I'm getting the error >>> >>> Error: >>> Problem: cannot install the best update candidate for package ceph- >> base-2:17.2.3-2.el9s.x86_64 >>> - nothing provides liburing.so.2()(64bit) needed by ceph-base- >> 2:17.2.6-4.el9s.x86_64 >>> - nothing provides liburing.so.2(LIBURING_2.0)(64bit) needed by >>> ceph- >> base-2:17.2.6-4.el9s.x86_64 >>> (try to add '--skip-broken' to skip uninstallable packages or '-- >> nobest' to use not only best candidate packages) >>> >>> Did Ceph Pacific switch to requiring liburing 2? Rocky 9 only >>> provides >> 0.7-7. CentOS stream seems to have 1.0.7-3 (at least back to when I >> set up that repo on Foreman; I don't remember if I'm keeping it up-to-date). >>> >>> Can I/should I just do --nobest when updating? I could probably >>> build >> it from a source RPM from another RH-based distro, but I'd rather keep >> it clean with the same distro. >>> _______________________________________________ > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |