[EPEL-devel] Re: State of EPEL mock chroots?
On Fri, 4 Feb 2022 at 12:12, Richard Shaw wrote: > On Fri, Feb 4, 2022 at 8:20 AM Stephen John Smoogen > wrote: > >> >> On Fri, 4 Feb 2022 at 09:05, Richard Shaw wrote: >> >>> I've gotten frequent requests to support EPEL branches of packages I >>> maintain for Fedora and I usually don't mind as long as it's "easy", >>> meaning build dep differences are minor and easy to work around, but mock >>> seems completely broken for EPEL and I don't like to support packages I >>> can't easily build. >>> >>> I know there's scratch builds, COPR, and stuff but I have a $DAYJOB and >>> nothing beats being able to test and iterate quickly using mock on my >>> workstation. >>> >>> Out of curiosity I just tried every EL 8 mock config and found the >>> following results: >>> >>> almalinux-8 works >>> centos-8broken (EOL) >>> centos-stream-8 works >>> epel-8-x86_64 broken >>> epel-next-8-x86_64 works >>> eurolinux-8-x86_64 works >>> oraclelinux-8-x86_64works >>> rhel-8-x86_64 no subscription >>> rockylinux works >>> >>> >> Check what /etc/mock/epel-8-x86_64.cfg is linked to on your system. If it >> is not linked to anything then it is going to be broken and either trying >> to use the Fedora koji or using data from CentOS mirrors which no longer >> exist. First step is decide which OS you will use to build EPEL packages >> against: Rocky, Alma, Oracle, RHEL. >> >> $ sudo -i >> # cd /etc/mock >> # mv epel-8-x86_64.cfg epel-8-x86_64-old.cfg >> # ln -s alma+epel-8-x86_64.cfg epel-8-x86_64.cfg >> >> Change alma+ to the OS you want to use. >> > > Ok, that's simple enough, but I have to ask the obvious question. :) > > Why isn't this fixed in the package? Though I do remember the thread Gary > referenced, still I would think it would be a good idea to choose ANY of > them if for no other reason than to not leave things broken. > > Because any choice was going to look like favoritism and people are rather particular about which OS they run. The mock people are caught in the middle and don't really want to be there. -- Stephen J Smoogen. Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren ___ 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: State of EPEL mock chroots?
On Fri, Feb 4, 2022 at 2:05 PM Richard Shaw wrote: > So most of them work, but not EPEL. That specific example is being tracked in RHBZ #2049024 The discussion started back in November 2021 https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/7T5N6SCPCWHNAUIFPFD54Z6CTLLZMJ6F/#7T5N6SCPCWHNAUIFPFD54Z6CTLLZMJ6F > So which SHOULD I be using for EPEL package development? I will note that mock-core-configs-36.4-1, which has been sitting in testing for some time (due to ongoing discussions and issues with some tooling, as I recall), and presumably the soon to be available next version of core configs have changed things around IRT the epel related mock cfgs (as I recall the new new version removes the epel-8 cfgs entirely, since they are, as you experienced, broken). The new normal for (at least) some use cases will be something of the form centos-stream+epel- ___ 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] how to do epel8 fedpkg mockbuild?
What do you need to do these days to run an epel-8 mock build? fedpkg mockbuild fails for me with Error: Error downloading packages: Status code: 403 for https://infrastructure.fedoraproject.org/repo/rhel/rhel8/koji/latest/x86_64/RHEL-8-001/non_modular/audit-libs-3.0-0.17.20191104git1c2f876.el8.x86_64.rpm (IP: 38.145.60.16) I configured a RHEL subscription key so that I can make a rhel-8 root successfully. ___ 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] pyproject-rpm-macros 1.0.0~rc1 available in EPEL 9 buildroot
Hello Pythonistats, just letting you know that as of today, I can finally see pyproject-rpm-macros-1.0.0~rc1-1.el9.noarch in the EPEL 9 Koji buildroot. That means, the %pyproject_* macros should now have identical features and behavior across Fedora and EPEL 9. Happy packaging, -- 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
