copr-devel August 2024

copr-devel@lists.fedorahosted.org

4 participants
5 discussions

Re: Early adopting EPEL 10 in Fedora Copr?
by Michael J Gruber 20 Aug '24

20 Aug '24

Neal Gompa venit, vidit, dixit 2024-08-15 16:14:30: > On Thu, Aug 15, 2024 at 9:45 AM Pavel Raiskup <praiskup(a)redhat.com> wrote: > > > > The epel-8-* and epel-9-* chroots in Fedora Copr are aliases > > to the "rhel+epel-*" chroots from `mock-core-configs` package. We'd > > like to have the same approach for `epel-10` once there's a released > > variant of RHEL 10 GA. > > > > For now though, there's the variant `centos-stream+epel-10` in the new > > mock-core-configs release, though: > > > > https://rpm-software-management.github.io/mock/Release-Notes-Configs-41.1 > > > > So we could make `epel-10-*` an alias to `centos-stream+epel-10` for the > > time being, and do the switch to `rhel+epel-10` later on. Do you think > > this makes sense? Or is it just too early? > > > > For EPEL 10, we would never do that switch. CentOS Stream + EPEL is > the default case for EPEL 10 now. RHEL + EPEL configs are the > alternative. > > So we would just have the alias and keep it "forever". I think we're mixing "mock core config name" and "copr chroot name" in this dicussion. epel-7-x86_64.cfg is the latest epel-* mock config I see in /etc/mock. Everything else is explicit (centos-stream+epel, rhel+epel, ...). The copr chroots epel-* etc always made me look twice what they actually are. Even switching the meaning "in between" makes it only. And I really think epel-* makes no sense since it's always "+" to something. EPEL guidelines spell out what is the official base distro for which EPEL (next or what not). That is something we could add next to the respective chroot in copr (just like the current remarks there). Cheers Michael

2 5

Fedora 41 chroots branched in Copr
by Pavel Raiskup 19 Aug '24

19 Aug '24

Hello, we branched Fedora 41 from Rawhide chroots in Copr. The following are now available: - fedora-41-aarch64 - fedora-41-i386 - fedora-41-ppc64le - fedora-41-s390x - fedora-41-x86_64 Pavel

1 0

Early adopting EPEL 10 in Fedora Copr?
by Pavel Raiskup 16 Aug '24

16 Aug '24

The epel-8-* and epel-9-* chroots in Fedora Copr are aliases to the "rhel+epel-*" chroots from `mock-core-configs` package. We'd like to have the same approach for `epel-10` once there's a released variant of RHEL 10 GA. For now though, there's the variant `centos-stream+epel-10` in the new mock-core-configs release, though: https://rpm-software-management.github.io/mock/Release-Notes-Configs-41.1 So we could make `epel-10-*` an alias to `centos-stream+epel-10` for the time being, and do the switch to `rhel+epel-10` later on. Do you think this makes sense? Or is it just too early? Pavel

1 1

EPEL6, Fedora ELN, and Mageia Cauldron
by Jakub Kadlcik 07 Aug '24

07 Aug '24

Hello, I did a small cleanup of old/broken chroots, so just that everybody knows: - I marked epel-6-i386 and epel-6-x86_64 as EOL (see previous email by msuchy) - I marked fedora-eln-i386 as EOL - I renamed mageia-cauldron-i586 chroot to mageia-cauldron-i686 Relevant tickets: [1] https://github.com/fedora-copr/copr/issues/3357 [2] https://github.com/fedora-copr/copr/issues/3354 [3] https://github.com/fedora-copr/copr/issues/3339 Jakub

1 0

EPEL 7 and EPEL 6 in Copr
by Miroslav Suchý 06 Aug '24

06 Aug '24

With EOL of RHEL 7 and EPEL 7 we recently got several questions how long we will keep epel-7-* chroots in Copr? It will stay in Copr as long as people will need it. I may start asking around this time next year. But for next 12 months do not expect a change. On the other hand we still have epel-6 enabled. And I checked several former users and it seems that no one is using it. Therefore we will disable epel-6 soon. -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel August 2024