Meeting started at 2026-06-24 18:01:12 UTC

The Meeting name is 'EPEL (2026-06-24)'

!hi

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

The Meeting Name is now epel

!hi

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

!hi

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

Hi Carl George

Hi Diego Herrera and Robby Callicotte

We're a little light, but still enough for a quorum.

We have one item marked for a meeting

!epel 367

● **Last Updated:** 5 minutes ago

**epel/steering #367** (https://forge.fedoraproject.org/epel/steering/issues/367):**(Slightly) incompatible update for EPEL 8 and 9: p7zip -> 7zip**

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

● **Assignee:** Not Assigned

Issue querying Pagure: Issue not found

There has been some discussion on the ticket. But we can discuss it more.

So it's shown in the meeting notes: There was a list of packages that needed to be looked at to see if the update affected them.

They were all tried in COPR, and the only one affected was GraphicsMagick.

Turns out it was more a bug of building GraphicsMagick on epel9 copr than the zip transition.

To me, it looks good to approve.

Does anyone else have any comments or thoughts?

i think some are missing

conky-manager and retrace-server

Oh, your right. He didn't do the whole list.

Michel Lind ☘ UTC+1 ⏱️: you around to talk about this one?

Oh, you are right. He didn't do the whole list.

Sounds like he's not.

Without the whole list tested, I think we should postpone voting on this until next week.

Ish

Huh, were those added later? Sorry. I didn't notice they were on the list

Can we approve this async if we get them in today?

nope, they were in the original list i grabbed

Ya. Async sounds good. I don't think we need to wait a whole week if they all pass.

Dealing with super annoying work outages, one sec

I might have them by end of meeting

Sounds good.

Does anyone have any other questions about this ticket?

i'm good

We have one other incompatible update. It's not due for vote, but I'm going to post it so people can take a quick look, and/or post some discussion on the ticket.

!epel 368

Issue querying Pagure: Issue not found

**epel/steering #368** (https://forge.fedoraproject.org/epel/steering/issues/368):**Proposed incompatible update / retirement: syncthing v1.30 -> v2**

● **Assignee:** Not Assigned

● **Last Updated:** Never

● **Opened:** 4 days ago by decathorpe

Again, this is due for next weeks meeting, but be sure to give it a look before then.

Ok we can go ahead

Conky manager and retrace server are not in epel9

I'll make sure to test them for epel8 if / when we get there

Oh, they are only in epel8 .... which you just said. :)

ah, sorry about that

then we should be ready to approve epel9, right?

I'm ok with that. Give it a partial approval for epel9. Then when/if epel8 COPR builds show things work, do an async approval for that?

It happens. I should have double checked against your list too and flag those as being epel8 only

That one can even be synchronous, I will take either. We don't need epel8 ourselves so it's just a community service at that point

+1 to epel9 proceeding (with appropriate announcements)

+1 for epel9 proceeding

+1

+1

I'm double checking. I'm quite sure we said majority passes.

Yep we did

Does someone want to write that up in the issue?

I'll wait for the write up before processing it

Much appreciated folks

I'll go for it :)

Diego Herrera: Thank you

That is our only marked issue ... moving on.

Does anyone have any old business?

salimma gave a cookie to dherrera. They now have 35 cookies, 5 of which were obtained in the Fedora 44 release cycle

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

Does anyone have anything for Open Floor?

carlwgeorge gave a cookie to dherrera. They now have 36 cookies, 6 of which were obtained in the Fedora 44 release cycle

rcallicotte gave a cookie to dherrera. They now have 37 cookies, 7 of which were obtained in the Fedora 44 release cycle

yselkowitz gave a cookie to dherrera. They now have 38 cookies, 8 of which were obtained in the Fedora 44 release cycle

for awareness, i've been doing lots of caddy work to resolve cves. epel10/epel10.2 are getting fast-forwarded to the f44 commit (same version). epel9/epel8 are going to be complicated.

as it stands they can't even be rebuilt at their current versions to pick up golang fixes, since golang has updated so much in el8/el9 since those were first built. i'll probably do an incompat update request for epel9, but for epel8 i'm leaning towards retirement because there it doesn't have go-vendor-tools to make it easier.

Talking about CVE's. qt6-qtwebengine in epel9 ... The KDE SIG has agreed to help me update it. I was planning on dropping it, but it turns out that there are several individuals/groups/companies that are using it directly, so dropping it would be bad.

I'm pretty sure the epel9 qt6-qtwebengine currently holds the record for most CVE's in EPEL.

It gives me stress.

Anything else for Open Floor?

I'll take the silence for a no. Let's call it a meeting.

Thank you all for coming today and for all the discussion. And thank you all for all you do for EPEL and it's community.

bye Troy!

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

bye ^^