[EPEL-devel] Re: python-gevent and pytest-cov in el9
On Sun, Sep 26, 2021 at 2:25 PM Miro Hrončok wrote: > > On 24. 09. 21 21:45, Ken Dreyer wrote: > > This means that python-pytest-cov and python-pytest-xdist won't be > > available on epel9, since those require gevent. > > Ignoring the rest of your email for now, but I don't the gevent dependency > does > not exsist: You're right, gevent is not a runtime requirement. pytest-xdist requires execnet, but execnet only BuildRequires gevent for the unit tests. So we could build execnet on el9 if we disabled %check and the "execmodel=gevent" feature. Maybe that's fine, since https://github.com/pytest-dev/execnet is almost unmaintained upstream, and users have opened unaddressed GitHub tickets in execnet and xdist regarding gevent hangs. This is another reason why I want to reduce Fedora's dependence on pytest-xdist and pytest-cov, if execnet is growing more unstable. - Ken ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: python-gevent and pytest-cov in el9
On 24. 09. 21 21:45, Ken Dreyer wrote: This means that python-pytest-cov and python-pytest-xdist won't be available on epel9, since those require gevent. Ignoring the rest of your email for now, but I don't the gevent dependency does not exsist: $ [dnf] install python3-pytest-cov python3-pytest-xdist ... Installed: expat-2.4.1-2.fc35.x86_64 mpdecimal-2.5.1-2.fc35.x86_64 openssl1.1-1:1.1.1l-1.fc36.x86_64 python-pip-wheel-21.2.3-2.fc36.noarch python-setuptools-wheel-57.4.0-1.fc35.noarch python3-3.10.0~rc2-2.fc36.x86_64 python3-attrs-21.2.0-4.fc35.noarch python3-coverage-5.6-0.3b1.fc35.x86_64 python3-execnet-1.9.0-2.fc35.noarch python3-iniconfig-1.1.1-5.fc35.noarch python3-libs-3.10.0~rc2-2.fc36.x86_64 python3-packaging-21.0-2.fc35.noarch python3-pluggy-1.0.0-1.fc36.noarch python3-py-1.10.0-5.fc35.noarch python3-pyparsing-2.4.7-9.fc35.noarch python3-pytest-6.2.5-1.fc36.noarch python3-pytest-cov-2.12.1-1.fc36.noarch python3-pytest-forked-1.3.0-4.fc35.noarch python3-pytest-xdist-2.4.0-1.fc36.noarch python3-setuptools-57.4.0-1.fc35.noarch python3-toml-0.10.2-5.fc35.noarch -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: python-gevent and pytest-cov in el9
On Fri, Sep 24, 2021 at 3:59 PM Josh Boyer wrote: > > 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 On the one hand, thank you for pointing out that this build is now available. That's good to know. On the other hand, this points at the bigger issue that dealing with the entire problem of missing packages requires a level of scripting and bookkeeping that is very difficult to keep up when building layered projects. > You could request libev-devel in the composes. The reason I did not do that in this case is that pytest-cov is an optional dependency, and we can just remove it from the Python packages instead. I'd rather reduce the dependencies on gevent to make everything faster. When I looked at gevent in EPEL 8 a month or so ago, it did not look like many packages depended on it. > 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 could point at https://kojihub.stream.centos.org/kojifiles/repos/c9s-build/latest/ , but that location will not have GPG-signed builds, and the repo is not currently in https://github.com/rpm-software-management/mock/blob/main/mock-core-configs/etc/mock/templates/centos-stream-9.tpl - Ken ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: python-gevent and pytest-cov in el9
On Fri, Sep 24, 2021 at 3:05 PM Josh Boyer wrote: > > On Fri, Sep 24, 2021 at 4:02 PM Neal Gompa wrote: > > > > On Fri, Sep 24, 2021 at 3:59 PM Josh Boyer wrote: > > > > > > On Fri, Sep 24, 2021 at 3:46 PM Ken Dreyer 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@lists.fedoraproject.org > To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: python-gevent and pytest-cov in el9
On Fri, Sep 24, 2021 at 1:03 PM Josh Boyer wrote: > On Fri, Sep 24, 2021 at 4:02 PM Neal Gompa wrote: > > > > On Fri, Sep 24, 2021 at 3:59 PM Josh Boyer wrote: > > > > > > On Fri, Sep 24, 2021 at 3:46 PM Ken Dreyer > 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. > EPEL9 will not be built again CentOS Stream 9, it will be built off RHEL 9. That is the EPEL policy. Thus, if something is not in RHEL 9, it is not available to be built in EPEL 9. It seems pretty straightforward. Troy ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: python-gevent and pytest-cov in el9
On Fri, Sep 24, 2021 at 4:09 PM Neal Gompa wrote: > > On Fri, Sep 24, 2021 at 4:03 PM Josh Boyer wrote: > > > > On Fri, Sep 24, 2021 at 4:02 PM Neal Gompa wrote: > > > > > > On Fri, Sep 24, 2021 at 3:59 PM Josh Boyer wrote: > > > > > > > > On Fri, Sep 24, 2021 at 3:46 PM Ken Dreyer > > > > 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. > > > > Well, because outside of RHEL, everyone wants remote and local builds > to have access to the same resources and not crush the servers. Since > buildroot stuff isn't going out on the mirror network (otherwise, why > would it be separate from CRB?), it's obvious we shouldn't rely on it > for packages that people should expect to be able to build and rebuild > for RHEL. So you have access to what you want, you have a way to pull it down and get it locally, but you can't depend on it because... you're worried a multi-billion dollar company can't pay it's server and CDN bills? As to why it's separate from CRB, that's because CRB is a reflection of what is provided as part of the product. It's that simple. > And again, by Red Hat's own sword (policy), RHEL doesn't want to ship > everything needed to build stuff, so if EPEL is intended to provide > the requisite community guarantees (reproducibly buildable), we have > to work with what RHEL gives us. I think that is also EPEL falling on EPEL's own sword a bit. I think it fails to recognize that building and distributing software can be separate things. I can see the need for a developer community to be able to build, update, and rebuild software it distributes. Access to the buildroots facilitates this. We could even point mock configs at it, or propose a buildroot repo for it if people are really worried about "servers". However, in the context of something like python-gevent, an EPEL *end user* isn't going to want libuv-devel or libev-devel to be installed on their system at runtime. They have no need for it to be available in a compose. They only need python-gevent and the requisite runtime libraries, which are already provided. I think separating the personas and thinking about the requirements for each might be worth doing. I understand this is a different approach and something that looks different from the past. It's been 2+ years since the OS EPEL8 is based on has shipped and it is taking a different approach than previous releases. Every indication we have shows the next major version will continue this. I'm worried that sticking with past policies precludes EPEL from making progress on a project that we all want to see succeed. josh ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: python-gevent and pytest-cov in el9
On Fri, Sep 24, 2021 at 4:03 PM Josh Boyer wrote: > > On Fri, Sep 24, 2021 at 4:02 PM Neal Gompa wrote: > > > > On Fri, Sep 24, 2021 at 3:59 PM Josh Boyer wrote: > > > > > > On Fri, Sep 24, 2021 at 3:46 PM Ken Dreyer 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. > Well, because outside of RHEL, everyone wants remote and local builds to have access to the same resources and not crush the servers. Since buildroot stuff isn't going out on the mirror network (otherwise, why would it be separate from CRB?), it's obvious we shouldn't rely on it for packages that people should expect to be able to build and rebuild for RHEL. And again, by Red Hat's own sword (policy), RHEL doesn't want to ship everything needed to build stuff, so if EPEL is intended to provide the requisite community guarantees (reproducibly buildable), we have to work with what RHEL gives us. -- 真実はいつも一つ！/ Always, there's only one truth! ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: python-gevent and pytest-cov in el9
On Fri, Sep 24, 2021 at 4:02 PM Neal Gompa wrote: > > On Fri, Sep 24, 2021 at 3:59 PM Josh Boyer wrote: > > > > On Fri, Sep 24, 2021 at 3:46 PM Ken Dreyer 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. josh ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: python-gevent and pytest-cov in el9
On Fri, Sep 24, 2021 at 3:59 PM Josh Boyer wrote: > > On Fri, Sep 24, 2021 at 3:46 PM Ken Dreyer 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. -- 真実はいつも一つ！/ Always, there's only one truth! ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: python-gevent and pytest-cov in el9
On Fri, Sep 24, 2021 at 3:46 PM Ken Dreyer 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. josh > (It's possible to package the missing -devel packages separately, and > I've been doing this by automatically following the NVR changes in > Stream 9's Koji for several weeks with scripts at > https://github.com/ktdreyer/ceph-el9. My conclusion is that it is so > painful that it's not sustainable to do this for years.) > > This means that python-pytest-cov and python-pytest-xdist won't be > available on epel9, since those require gevent. > > Several Python packages require python-pytest-cov because upstream > lists it in requirements.txt or tests-requirements.txt. I think we > should just patch these out in Fedora. Even apart from RHEL's > restrictions, it's not a good use of resources to run pytest-cov when > no one reviews coverage reports in the Koji logs, and we'll speed up > builds when mock doesn't have to install this spurious BuildRequires. > > Here are a list of packages where I've removed pytest-cov: > > https://src.fedoraproject.org/rpms/python-watchdog/pull-request/4 > https://src.fedoraproject.org/rpms/python-cheroot/pull-request/15 > https://src.fedoraproject.org/rpms/python-portend/pull-request/5 > https://src.fedoraproject.org/rpms/python-typing-extensions/pull-request/3 > > - Ken > ___ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
