Meeting started at 2026-07-15 18:00:58 UTC

The Meeting name is 'EPEL (2026-07-15)'

!hi

Carl George: Carl George (carlwgeorge) - he / him / his

!hi

Robby Callicotte: Robby Callicotte (rcallicotte) - he / him / his

The Meeting Name is now epel

!hi

Diego Herrera: Diego Herrera (dherrera) - he / him / his

Oh ... two of you beat me to the topic. :)

Hi Carl George Robby Callicotte and Diego Herrera

whoops, forgot again

tbh, I waited for it ;)

Sorry

I don't really care ... I just thought you were racing me.

We're a little light, but we have enough for a quorum and a majority vote ... so let's get going.

Let's start with the older open issue first.

!epel 369

**epel/steering #369** (https://forge.fedoraproject.org/epel/steering/issues/369):**(Slightly) Incompatible update request for rust-routinator**

● **Opened:** a week ago by salimma

● **Assignee:** Not Assigned

● **Last Updated:** 10 hours ago

Issue querying Pagure: Issue not found

We talked a little about this last week, and said we could give it +1's in the ticket, which several people did, but it never got up to a majority.

i just gave it a +1 too

Was there anything we wanted to talk about it, or are we good?

me too

Looks like it's passed then.

Robby Callicotte: did you want to vote on it as well?

looks like the fesco issue (i'm assuming for f44/f43, doesn't actually say) is going to pass as well

OK, I've close that one, not on to the other one.

!epel 370

● **Last Updated:** 52 minutes ago

**epel/steering #370** (https://forge.fedoraproject.org/epel/steering/issues/370):**EPEL9 Incompatible Update - ffmpeg 5 to 7**

● **Opened:** a week ago by tdawson

● **Assignee:** Not Assigned

Issue querying Pagure: Issue not found

OK, I've close that one, now on to the other one.

This one is mine. I've switched it from epel9 to epel9-next.

gave this one a late +1 as well. i like the idea of doing it in epel9-next first.

I think it will give me more time for all the updates and such, but it does add the complication that I don't own all the packages.

Diego Herrera made me realize yesterday that epel9-next will be retired in less than a year

Ya, it's sorta crazy how quick it's gone by

I'm giving this a +1 as well ... but I think that's sorta a given.

Robby Callicotte: or Diego Herrera Do either of you have questions?

I'm quite sure Conan Kudo 😌 would give this one a +1, but that's not official, so I can't count it.

No questions from me

+1

I had one, noticed that someone pointed out about 5.1.10 update on the mailing list

now that we pinged neal i bet he shows up to vote in the next few minutes

I imagine that the patch update doesn't fix the underlying issues, right?

Ya, I'm going to try to get the regular ffmpeg for epel9 updated to 5.1.10 (which isn't incompatible) soon.

if so, +1 from me

checking ...

Yes, it looks like the one that is currently in epel10 has the fixes.

but... tbh, maybe i'm being overly nitpicky if the plan is to land it in epel9-next beforehand, let's go with +1 :)

but... tbh, maybe i'm being overly nitpicky if the plan is to land it in epel9-next, let's go with +1 :)

Well, I do want it to have the latest updates and patches for that version of ffmpeg, but updating the ffmpeg in epel9 to 5.1.10 would be something seperate.

Moving on.

Does anyone have any Old Business?

I'll take that as a no ... moving on.

Does anyone have anything for Open Floor?

i'm working on a discussion thread to talk about metalinks and baseurls in epel11, not done yet but be on the look out for that later this week or early next week

OK. but not you've got me curious.

inspired by comments like this https://bugzilla.redhat.com/show_bug.cgi?id=2494597#c6

basically users that are mirroring directly by url (like with satellite/foreman) for rhel usage are grumpy that the long standing pattern of `pub/epel/$major` changed

Understandable ... and I looks forward to your email.

they have a point, it's just unfortunate that feedback is coming in so long after things were implemented

i have a plan of how we can remediate that in epel11, which will have a nice side effect of simplifying some of the releng work

Yep ... maybe having 11 be the default, and 11.y be centos-stream based.

more like 11 and 11s (or some other character), but yes

That came out wrong ... oh ... 11s does sound better.

unfortunately dnf doesn't have the inverse of what we're using now (releasever_minor), so doing that will involve keying of the stream variable. nothing functionally wrong with that, it just makes that variable more load bearing.

that came out weird, what i mean is dnf logic (like the bash logic it's based on) lets us insert a string if a variable is set, but not if the variable is not set

I kinda feel that changing this and then changing it again is more disruptive than just telling people it's different now

This is one of things that we look back and go ... well ya ... I think 10, 10s, 10.1 .... and yet we discussed this for months and it didn't even occure to my mind.

now being for 10 and later

yeah, hindsight things

i get that angle. if i get agreement in esc around how to do this in 11, i also have an idea about how to switch 10 to the same thing smoothly. if we did that, then rhel users who lag behind and haven't touched anything 10 yet (the vast majority of them) will never be exposed to the change.

that will be a separate discussion thread though 😉

fair enough. I literally just shipped the fedrq changes for EPEL 10 yesterday so now I'm just thinking... wait a minute

when i get the thread up definitely chime in with the implications to tools like that

👍️

I just did a check to see if things have changed ... it's still 10 - 100,000 machines, 9 - 3,500,000 machines ... so ya ... the majority of users haven't switched to 10 yet.

Sorry, I should have stated, those are CentOS STream numbers, nothing to do with EPEL.

But it gives a rough estimate of 10 versus 9 statistics.

on the rhel side, rhel 7 was the most popular rhel major until a year after its eol. now it's rhel8, and probably will be for a long while.

Yep ... there is a reason users use an enterprise release, and it's not to be running the new stuff.

Anyway ... anything else for Open Floor?

The silence vote wins ... time for an end the meeting.

Thank you all for the good discussions, and thank you for all you do for EPEL and it's community.

I'll talk to you next week, if not sooner.

Bye Troy.