EPEL 10 work tracker

If you want to take an item to work on, please leave a comment

needs investigation

intermittent errors processing epel10 branch requests (possibly not epel10-specific, possibly not worth investigating because of the upcoming git forge change)
- https://pagure.io/releng/fedora-scm-requests/issue/64279#comment-923107
- https://pagure.io/releng/fedora-scm-requests/issue/64367#comment-923376
- https://pagure.io/releng/issue/12108 (similar failure for new repo request)
- https://pagure.io/releng/fedora-scm-requests/issue/72306#comment-955831
is there a way to prevent packagers pushing to branches they haven't requested?
koschei support
- https://github.com/fedora-infra/koschei/issues/362

epel-release demo

You can see a demo of the releasever_major/minor variables by running a few commands inside a c10 container.

podman run -it --rm centos:stream10-development

cat >> /etc/yum.repos.d/epel.repo << EOF
[epel]
name=Extra Packages for Enterprise Linux \$releasever - \$basearch
gpgcheck=0
baseurl=https://carlwgeorge.fedorapeople.org/repos/epel\$releasever_major\${releasever_minor:+.\$releasever_minor}/\$basearch/
EOF
dnf --repo epel repolist
dnf --repo epel repoquery --quiet --nvr hello

Note the repo name of Extra Packages for Enterprise Linux 10 - x86_64 and the package nvr of hello-2.12.1-4.el10_1.

echo 10.0 > /etc/dnf/vars/releasever
dnf --repo epel repolist
dnf --repo epel repoquery --quiet --nvr hello

Note the repo name of Extra Packages for Enterprise Linux 10.0 - x86_64 and the package nvr of hello-2.12.1-4.el10_0.

approximate availability and EOL dates

EPEL	CentOS	RHEL	EOL
10.0	2024-??-??	2025-05-??	2025-11-31
10.1	2025-03-??	2025-11-??	2026-05-31
10.2	2025-09-??	2026-05-??	2026-11-31
10.3	2026-03-??	2026-11-??	2027-05-31
10.4	2026-09-??	2027-05-??	2027-11-31
10.5	2027-03-??	2027-11-??	2028-05-31
10.6	2027-09-??	2028-05-??	2028-11-31
10.7	2028-03-??	2028-11-??	2029-05-31
10.8	2028-09-??	2029-05-??	2029-11-31
10.9	2029-03-??	2029-11-??	2030-05-31
10.10	2029-09-??	2030-05-??	2035-05-31

mass-branching tooling - Diego?

Fedora SOP
Fedora checklist
will need minor version work
SOP follow up tweaks:

tag creation script

create an epel version of this

https://pagure.io/releng/blob/main/f/scripts/branching/make-koji-release-tags

releng work for EPEL minor versions

references

EPEL 9 buildroot reconfiguration

miscellaneous references

https://docs.pagure.org/koji/tag_inheritance/
https://docs.fedoraproject.org/en-US/infra/release_guide/release_eol/
bodhi can return all current EPEL 10 releases with a special API call
- http https://bodhi.fedoraproject.org/releases/ name==EPEL-10% state==current
- http https://bodhi.fedoraproject.org/releases/ name==EPEL-10% state==pending

packages.fp.o

Carl George

2024/03/20 19:54:05

mockconfig = ‘epel-10-x86_64’ or ‘epel-10.1-x86_64

I believe we'll need both. While in the build system the resulting dist tag will always have an underscore and minor version, we won't be able to derive that solely from the branch name when it's epel10. We'll need fedpkg to resolve like so: - epel10 branch -> epel-10-$arch mockconfig - epel10.0 branch -> epel-10.0-$arch mockconfig - and so on