On Mon, Nov 22, 2021 at 8:27 AM Miroslav Suchý <msuchy(a)redhat.com> wrote:
Dne 22. 11. 21 v 15:10 Miro Hrončok napsal(a):
>
> However, enough of my personal views. Since we have not used RHEL for copr/mock EPEL
buidlroots until now, but we used
> a downstream freely-available RHEL-copy (CentOS Linux), could we not continue doing
so by using e.g. AlmaLinux?
For day to day work I would suggest to move to centos-stream + epel-next (hmm, we do not
have a config for that).
But EPEL is built against RHEL (not Alma, not Rocky). So we either use default config
which will differ from Koji or we
have to fiddle with entitlements:
https://rpm-software-management.github.io/mock/Feature-rhelchroots
https://developers.redhat.com/blog/2021/02/10/how-to-activate-your-no-cos...
Miroslav
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Agreed, for quick local builds it's fine to use epel8-next (c8s) to
verify it builds and then submit the koji build to the epel8 (rhel8)
target. If the local build works but the koji build doesn't, you
likely have a candidate for an official epel8-next koji build.
--
Carl George