[EPEL-devel] Re: Upcoming EPEL 10.0 retirement

2025-11-11 Thread Carl George
On Tue, Nov 4, 2025 at 9:13 PM Carl George  wrote:
>
> Howdy EPEL packagers,
>
> In accordance with the EPEL policy for minor version end-of-life [0],
> EPEL 10.0 will be retired once RHEL 10.1 is released.  Based on
> historical RHEL release dates [1], this is expected to occur sometime
> this month.  After the retirement, MirrorManager will direct RHEL 10
> users to the EPEL 10.1 repo instead.
>
> Similar to a Fedora release end-of-life, any EPEL 10.0 updates that
> have not been pushed to stable by the time of the retirement will be
> marked as obsolete and will not be promoted to stable.  Additionally,
> any outstanding epel10.0 side tags will be removed during the
> retirement.
>
> This is the first time an EPEL minor version will be retired, so
> thanks in advance for your patience as we establish the process for
> this.  If you have any questions, feel free to reply here or stop by
> the EPEL Matrix channel [2].
>
> [0] 
> https://docs.fedoraproject.org/en-US/epel/epel-policy/#policy_for_end_of_life_releases
> [1] https://access.redhat.com/articles/red-hat-enterprise-linux-release-dates
> [2] https://matrix.to/#/#epel:fedoraproject.org
>
> --
> Carl George

RHEL 10.1 was released earlier today, so as planned EPEL 10.0 has been
retired.  There is some remaining clean up work in the infrastructure
remaining, but all the user and maintainer facing changes have been
completed.

-- 
Carl George

-- 
___
epel-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


[EPEL-devel] Re: Upcoming EPEL 10.0 retirement

2025-11-11 Thread Carl George
On Tue, Nov 11, 2025 at 11:26 AM Chris Adams  wrote:
>
> Once upon a time, Diego Herrera  said:
> > Since RHEL 10.1 is starting to be available through several channels, we 
> > are going to start the retirement of the 10.0 branch and the archival of 
> > the 10.0 content. Also we are going to prepare the infrastructure so that 
> > EPEL 10.1 content will start being built from RHEL 10.1. All these changes 
> > will be done in accordance to the defined SOP [0]
> >
> > If you have any questions, feel free to reply here or stop by the EPEL 
> > Matrix channel [1].
>
> I updated a VM to RHEL 10.1, see /etc/os-release clearly says 10.1...
> but dnf is still using 10.0 for EPEL.  It looks like dnf is fetching the
> following URL from mirrormanager:
>
>https://mirrors.fedoraproject.org/metalink?repo=epel-z-10&arch=x86_64
>
> The URL in the repo file is:
>
>
> https://mirrors.fedoraproject.org/metalink?repo=epel${releasever_minor:+-z}-$releasever&arch=$basearch
>
> I thought $releasever should be 10.1 on RHEL, not just 10.
>
> --
> Chris Adams 
> --
> ___
> epel-devel mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> 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/[email protected]
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue

Switching the mirrormanager repo redirects to 10.1 is part of the
process we're doing today.

https://docs.fedoraproject.org/en-US/infra/release_guide/sop_epel_minor_eol/#_mirror_tasks

The original idea way back when we were first planning EPEL 10 was
that systems could just request an EPEL minor version matching their
system.  We realized later that would lead to upgrade path issues, so
we had to adjust the plan.

https://pagure.io/epel/issue/324

We have no control over $releasever, that is set to 10 by RHEL itself
unless you override it to a specific minor release.

-- 
Carl George

-- 
___
epel-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


[EPEL-devel] Re: Upcoming EPEL 10.0 retirement

2025-11-11 Thread Chris Adams
Once upon a time, Diego Herrera  said:
> Since RHEL 10.1 is starting to be available through several channels, we are 
> going to start the retirement of the 10.0 branch and the archival of the 10.0 
> content. Also we are going to prepare the infrastructure so that EPEL 10.1 
> content will start being built from RHEL 10.1. All these changes will be done 
> in accordance to the defined SOP [0]
> 
> If you have any questions, feel free to reply here or stop by the EPEL Matrix 
> channel [1].

I updated a VM to RHEL 10.1, see /etc/os-release clearly says 10.1...
but dnf is still using 10.0 for EPEL.  It looks like dnf is fetching the
following URL from mirrormanager:

   https://mirrors.fedoraproject.org/metalink?repo=epel-z-10&arch=x86_64

The URL in the repo file is:

   
https://mirrors.fedoraproject.org/metalink?repo=epel${releasever_minor:+-z}-$releasever&arch=$basearch

I thought $releasever should be 10.1 on RHEL, not just 10.

-- 
Chris Adams 
-- 
___
epel-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


[EPEL-devel] Re: Upcoming EPEL 10.0 retirement

2025-11-11 Thread Diego Herrera
Hello EPEL packagers

Since RHEL 10.1 is starting to be available through several channels, we are 
going to start the retirement of the 10.0 branch and the archival of the 10.0 
content. Also we are going to prepare the infrastructure so that EPEL 10.1 
content will start being built from RHEL 10.1. All these changes will be done 
in accordance to the defined SOP [0]

If you have any questions, feel free to reply here or stop by the EPEL Matrix 
channel [1].

[0] https://docs.fedoraproject.org/en-US/infra/release_guide/sop_epel_minor_eol/
[1] https://matrix.to/#/#epel:fedoraproject.org
-- 
___
epel-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue