On Fri, Sep 24, 2021 at 3:05 PM Josh Boyer <jwboyer@xxxxxxxxxx> wrote: > > On Fri, Sep 24, 2021 at 4:02 PM Neal Gompa <ngompa13@xxxxxxxxx> wrote: > > > > On Fri, Sep 24, 2021 at 3:59 PM Josh Boyer <jwboyer@xxxxxxxxxx> wrote: > > > > > > On Fri, Sep 24, 2021 at 3:46 PM Ken Dreyer <ktdreyer@xxxxxxxxxxxx> wrote: > > > > > > > > Hi folks, > > > > > > > > The RHEL 9 composes do not have libev-devel and libuv-devel, so we > > > > cannot build python-gevent on EPEL 9 easily. > > > > > > https://odcs.stream.centos.org/production/CentOS-Stream-9-20210924.0/compose/CRB/x86_64/os/Packages/libuv-devel-1.42.0-1.el9.x86_64.rpm > > > > > > You could request libev-devel in the composes. I remain confused why > > > it has to be in the compose though, because libev and it's devel > > > package are accessible in the CentOS Stream 9 buildroots today. > > > > > > > We can't use them in EPEL if they're not in CRB. > > Yes, that's what everyone keeps telling me. I don't understand why. EPEL builds against published RHEL content, not the CentOS Stream buildroot. Having a package available in the CentOS Stream buildroot doesn't make it accessible to EPEL builds. We can't change EPEL to use the CentOS Stream buildroot because that will cause some EPEL packages to not be installable on RHEL. On a related note, EPEL 9 Next _is_ being set up to build against the CentOS Stream 9 buildroot. This works for EPEL Next because it explicitly targets the next minor release of RHEL (i.e. CentOS Stream). This will allow more packages to be built, at the cost of potentially confusing packagers when their package builds successfully for EPEL 9 Next but not for EPEL 9. EPEL 8 Next currently builds against published CentOS Stream 8 content. If things go well with EPEL 9 Next using the CentOS Stream 9 buildroot, EPEL 8 Next may switch to using the CentOS Stream 8 buildroot in the future. > > josh > _______________________________________________ > epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
