[EPEL-devel] Fedora EPEL 7 updates-testing report

2023-03-31 Thread updates
The following Fedora EPEL 7 Security updates need testing: Age URL 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-9a3db4278b openbgpd-7.9-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing chromium-111.0.5563.146-1.el7 seamonkey-2.53.16-1.el

[EPEL-devel] Re: Creating an epelrelease dnf variable

2023-03-31 Thread Troy Dawson
On Fri, Mar 31, 2023 at 11:19 AM Miroslav Suchý wrote: > Dne 31. 03. 23 v 16:42 Troy Dawson napsal(a): > > How to set it, I suggest triggers. But that needs a bit more > investigation and testing. > > May I suggest file trigger? > > https://rpm-software-management.github.io/rpm/manual/file_trigg

[EPEL-devel] Re: Creating an epelrelease dnf variable

2023-03-31 Thread Miroslav Suchý
Dne 31. 03. 23 v 16:42 Troy Dawson napsal(a): How to set it, I suggest triggers.  But that needs a bit more investigation and testing. May I suggest file trigger? https://rpm-software-management.github.io/rpm/manual/file_triggers.html Miroslav ___

[EPEL-devel] Re: EPEL2RHEL - New Wording? - New Workflow?

2023-03-31 Thread Carl George
That sounds great, thanks. On Thu, Mar 30, 2023, 8:28 AM Troy Dawson wrote: > It doesn't look like they've done their merge yet, so I'll see if I can > get your change in. > How does this sound? > > Subject: > Notice: will be automatically retired from EPEL when > RHEL . is released > > Commen

[EPEL-devel] Creating an epelrelease dnf variable

2023-03-31 Thread Troy Dawson
This is mainly for EPEL10 planning, but others might find it useful, so I'm sending it to the email vs the epel10 discussion on discourse. I was talking with Carl about creating a dnf variable for the epel 10 repos. He had been talking about using $releasever and $releaseminor. But we also talke