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-8 broken (EOL) centos-stream-8 works epel-8-x86_64 broken epel-next-8-x86_64 works eurolinux-8-x86_64 works oraclelinux-8-x86_64 works rhel-8-x86_64 no subscription rockylinux works
So most of them work, but not EPEL. So which SHOULD I be using for EPEL package development?
Thanks, Richard
On Fri, 4 Feb 2022 at 09:05, Richard Shaw hobbes1069@gmail.com 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-8 broken (EOL) centos-stream-8 works epel-8-x86_64 broken epel-next-8-x86_64 works eurolinux-8-x86_64 works oraclelinux-8-x86_64 works 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.
So most of them work, but not EPEL. So which SHOULD I be using for EPEL package development?
Thanks, Richard _______________________________________________ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-leave@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... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Fri, Feb 4, 2022 at 8:20 AM Stephen John Smoogen smooge@gmail.com wrote:
On Fri, 4 Feb 2022 at 09:05, Richard Shaw hobbes1069@gmail.com 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-8 broken (EOL) centos-stream-8 works epel-8-x86_64 broken epel-next-8-x86_64 works eurolinux-8-x86_64 works oraclelinux-8-x86_64 works 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.
Thanks, Richard
On Fri, 4 Feb 2022 at 12:12, Richard Shaw hobbes1069@gmail.com wrote:
On Fri, Feb 4, 2022 at 8:20 AM Stephen John Smoogen smooge@gmail.com wrote:
On Fri, 4 Feb 2022 at 09:05, Richard Shaw hobbes1069@gmail.com 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-8 broken (EOL) centos-stream-8 works epel-8-x86_64 broken epel-next-8-x86_64 works eurolinux-8-x86_64 works oraclelinux-8-x86_64 works 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.
On Fri, Feb 4, 2022 at 5:12 PM Richard Shaw hobbes1069@gmail.com wrote:
Why isn't this fixed in the package?
Because the community never achieved a consensus as to what to do, as there were no proposals that did not include notable objections (and some of the required fixes to tooling for some of the approaches were still, I believe, a work in progress (although soon)).
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.
As noted in the announcement for the next new mock release (and core configs) everything is different all over again.... We shall see if this newer update will reach stable, or other issues are identified that will need to be addressed. Discussed here:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/...
along with the related ticket RHBZ #2026571
It appears the upstream has a few additional configurations for centos-stream+epel that I would like to see get in sooner rather than later just to address some taxonomy consistency, but they are not really critical.
As an aside, I will also note that the rpmfusion mock configs will probably need to adjust to the new names once the mock core config changes get to stable. That may result in some new mock opportunities for you going forward.
On Fri, Feb 4, 2022 at 2:05 PM Richard Shaw hobbes1069@gmail.com 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/devel@lists.fedoraproject.org/...
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@lists.fedoraproject.org
-
Gary Buhrmaster -
Richard Shaw -
Stephen John Smoogen