Re: [EPEL-announce] Re: EPEL 10.2 mass branching

[Orion Poplawski]

I'm getting:

Builds : Cannot find release associated with build: 
python-pytest-xprocess-1.0.2-5.el10_3, tags: ['epel10.3-testing-candidate']

when trying to submit a 10.3 update

On 2/23/26 15:33, Carl George via epel-announce wrote:
> We have completed mass branching for epel10.2.
>
> The epel10-candidate target has been restored, and you can resume
> building from the epel10 branch. Doing so will result in builds for
> EPEL 10.3. EPEL 10.2 builds that were submitted before the branching
> point are being tracked and will get tagged into epel10.3 once they
> reach stable status and get the epel10.2 tag.
>
> If you still want to build specifically for EPEL 10.2, you can build
> from the epel10.2 branch. If you request an epel10 branch for a
> package after this point, the epel10.2 branch will not be created
> automatically and must be requested separately.
>
> Thanks for your patience and happy packaging!
>
> On Mon, Feb 23, 2026 at 9:29 AM Diego Herrera via epel-announce
>  wrote:
> > Hello EPEL packagers,
> >
> > We are beginning the epel10.1 mass branching process.
> > Builds to the epel10-candidate target are now disabled until we finish the branching process.
> >
> > epel-announce mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]...
> > Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new

[EPEL-announce] Re: EPEL 10.2 mass branching

[Carl George]

It seems our SOP was missing a flag for the bodhi playbook.  I re-ran
it with that, and that seems to have resolved the problem.  I went
ahead and created that update for you to confirm it worked.

https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-65cc508e5c

Sorry for the trouble.

On Mon, Feb 23, 2026 at 8:07 PM Orion Poplawski  wrote:
> I'm getting:
>
> Builds : Cannot find release associated with build:
> python-pytest-xprocess-1.0.2-5.el10_3, tags: ['epel10.3-testing-candidate']
>
> when trying to submit a 10.3 update
>
> On 2/23/26 15:33, Carl George via epel-announce wrote:
> > We have completed mass branching for epel10.2.
> >
> > The epel10-candidate target has been restored, and you can resume
> > building from the epel10 branch. Doing so will result in builds for
> > EPEL 10.3. EPEL 10.2 builds that were submitted before the branching
> > point are being tracked and will get tagged into epel10.3 once they
> > reach stable status and get the epel10.2 tag.
> >
> > If you still want to build specifically for EPEL 10.2, you can build
> > from the epel10.2 branch. If you request an epel10 branch for a
> > package after this point, the epel10.2 branch will not be created
> > automatically and must be requested separately.
> >
> > Thanks for your patience and happy packaging!
> >
> > On Mon, Feb 23, 2026 at 9:29 AM Diego Herrera via epel-announce
> >  wrote:
> > > Hello EPEL packagers,
> > >
> > > We are beginning the epel10.1 mass branching process.
> > > Builds to the epel10-candidate target are now disabled until we finish the branching process.
> > >
> > > epel-announce mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]...
> > > Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
>
> --
> Orion Poplawski
> he/him/his  - surely the least important thing about me
> IT Systems Manager                         720-772-5637
> NWRA, Boulder/CoRA Office             FAX: [phone]
> 3380 Mitchell Lane                       [e-mail]
> Boulder, CO 80301                 https://www.nwra.com/