#meeting-1:fedoraproject.org log

<@tdawson:fedora.im>

17:59:56

!startmeeting EPEL (2025-08-13)

<@meetbot:fedora.im>

18:00:00

Meeting started at 2025-08-13 17:59:56 UTC

<@meetbot:fedora.im>

18:00:01

The Meeting name is 'EPEL (2025-08-13)'

<@carlwgeorge:fedora.im>

18:00:04

!hi

<@tdawson:fedora.im>

18:00:06

!meetingname epel

<@tdawson:fedora.im>

18:00:06

!topic aloha

<@meetbot:fedora.im>

18:00:08

The Meeting Name is now epel

<@zodbot:fedora.im>

18:00:08

Carl George (carlwgeorge) - he / him / his

<@tdawson:fedora.im>

18:00:17

Hi Carl George

<@rcallicotte:fedora.im>

18:00:19

!hi

<@dherrera:fedora.im>

18:00:21

!hi

<@zodbot:fedora.im>

18:00:21

Robby Callicotte (rcallicotte) - he / him / his

<@zodbot:fedora.im>

18:00:22

Diego Herrera (dherrera) - he / him / his

<@tdawson:fedora.im>

18:00:39

Hi Robby Callicotte and Diego Herrera

<@tdawson:fedora.im>

18:03:15

Is there a conference going on this week?

<@tdawson:fedora.im>

18:03:41

Jonathan is at one ... so I guess there is at least one.

<@tdawson:fedora.im>

18:05:12

Maybe more people will join in a bit

<@tdawson:fedora.im>

18:05:15

!topic EPEL Issues https://pagure.io/epel/issues

<@tdawson:fedora.im>

18:05:15

!link https://pagure.io/epel/issues?tags=meeting&status=Open

<@tdawson:fedora.im>

18:05:53

There is not anything marked for meeting in the issues or pull requests.

<@tdawson:fedora.im>

18:06:05

!topic Old Business

<@tdawson:fedora.im>

18:06:05

<@tdawson:fedora.im>

18:06:26

Do we have any Old Business?

<@tdawson:fedora.im>

18:07:34

Everyone is being nice and quiet, hoping for a short meeting.

<@rcallicotte:fedora.im>

18:08:06

<@nirik:matrix.scrye.com>

18:08:17

there was some kind of server lag here... I just got all the messages from the meeting start.

<@davide:cavalca.name>

18:08:33

!hi

<@zodbot:fedora.im>

18:08:34

Davide Cavalca (dcavalca) - he / him / his

<@tdawson:fedora.im>

18:08:38

Morning nirik

<@tdawson:fedora.im>

18:08:46

Hi Davide Cavalca

<@nhanlon:beeper.com>

18:09:10

!hi

<@zodbot:fedora.im>

18:09:12

Neil Hanlon (neil) - he / him / his

<@tdawson:fedora.im>

18:09:18

Hi Neil Hanlon

<@tdawson:fedora.im>

18:09:38

Now that we have more people ... any Old Business? Or are we ready for Open Floor.

<@nhanlon:beeper.com>

18:09:40

aloha, friends

<@tdawson:fedora.im>

18:10:59

Hopefully the long pause is because there isn't any Old Business, and not because of server lag ... moving on.

<@tdawson:fedora.im>

18:11:10

!topic General Issues / Open Floor

<@tdawson:fedora.im>

18:11:44

I do have one thing for Open Floor.

<@tdawson:fedora.im>

18:12:09

I will not be around next week. Does anyone want to run the meeting next week?

<@nhanlon:beeper.com>

18:12:23

_will also be away_

<@carlwgeorge:fedora.im>

18:12:33

i can do it

<@tdawson:fedora.im>

18:12:43

Carl George: Thank you

<@carlwgeorge:fedora.im>

18:14:22

i've got an open floor item

<@tdawson:fedora.im>

18:14:30

Carl George: Go for it.

<@carlwgeorge:fedora.im>

18:15:13

me and Diego Herrera are currently planning to do the epel10.1 mass branching on august 25th, and are doing prep work now

<@carlwgeorge:fedora.im>

18:15:17

https://codeberg.org/fedora/epel/milestone/18075

<@rcallicotte:fedora.im>

18:15:53

nice

<@carlwgeorge:fedora.im>

18:16:25

after that happens, we'll have a short period of triple branches, and then when rhel10.1 is released we'll drop back down to two as epel10.0 will be deactivated

<@nirik:matrix.scrye.com>

18:16:27

cool. let me know if I can assist with anything...

<@tdawson:fedora.im>

18:16:54

During that time, we will not be able to build for epel10.1, correct ?

<@carlwgeorge:fedora.im>

18:17:00

i'm sure we'll run into something unexpected and will appreciate the assist

<@tdawson:fedora.im>

18:17:20

During the triple branched time is what I meant.

<@carlwgeorge:fedora.im>

18:17:43

during the mass branching we'll delete the epel10 target, and then recreate it at the end

<@carlwgeorge:fedora.im>

18:18:05

while there are three branches, maintainers will be able to build for all three

<@tdawson:fedora.im>

18:18:33

Oh really? Cool.

<@tdawson:fedora.im>

18:18:50

Oh, that's right, you create a snapshot of centos stream right when you branch.

<@carlwgeorge:fedora.im>

18:19:02

i would advise maintainers to just build from the epel10 branch at that time, and leave epel10.1 as-is

<@carlwgeorge:fedora.im>

18:19:23

sort of like rhel itself (although we don't enforce any kind of freeze on the epel side)

<@rcallicotte:fedora.im>

18:20:11

This sounds neat

<@nhanlon:beeper.com>

18:21:03

love it

<@nirik:matrix.scrye.com>

18:21:45

from time to time people do pop up that are confused by the epel10/10.1 plan... but there's only so much documentating and announcing you can do. ;)

<@carlwgeorge:fedora.im>

18:22:37

yeah gradually people pop up that haven't been paying attention for the last few years of planning

<@rcallicotte:fedora.im>

18:22:39

Yeah I think the message has been repeated over and over for months and months.

<@carlwgeorge:fedora.im>

18:23:05

https://docs.fedoraproject.org/en-US/epel/branches/ is my go-to explainer, along with conference talk recordings

<@dherrera:fedora.im>

18:23:39

now, when rhel 10.1 releases, the idea is to archive 10.0, so if there are specific fixes/bugs/cves that you want to get there before that happens, you have to look out for that

<@carlwgeorge:fedora.im>

18:24:18

i have been thinking about an epel package maintenance guide to pair with https://docs.fedoraproject.org/en-US/package-maintainers/Package_Maintenance_Guide/ and note differences and provide workflow examples, but it's not written yet

<@carlwgeorge:fedora.im>

18:25:10

as always, if other people have ideas for how to improve the documentation, i'm all ears

<@carlwgeorge:fedora.im>

18:25:38

our faq definitely needs a big refresher, drop obsolete stuff, and add epel10 stuff

<@tdawson:fedora.im>

18:26:03

Yep

<@nirik:matrix.scrye.com>

18:26:38

Might be worth a blog post and/or announce post about the branching ?

<@tdawson:fedora.im>

18:28:00

Anything else for Open Floor?

<@carlwgeorge:fedora.im>

18:28:23

if you mean the mass branching, yes i'll announce that like last time

<@carlwgeorge:fedora.im>

18:28:38

i'm not sure how much lead time i should give for that, as the date may change

<@nirik:matrix.scrye.com>

18:29:00

I'm sure there will be some folks confused by it... but yeah.

<@carlwgeorge:fedora.im>

18:30:04

just double checked, and our outside factors leading to that date are still the same, so as of now it's still happening on the 25th

<@rcallicotte:fedora.im>

18:30:21

I think 7 days at least would be sufficient

<@rcallicotte:fedora.im>

18:31:32

Or would it be a good idea to have some sort of calendar of events?? Similar to the Fedora release calandar?

<@rcallicotte:fedora.im>

18:32:03

Sorry, the release schedule I mean

<@nirik:matrix.scrye.com>

18:32:24

I think that would be nice... not sure the tooling involved tho

<@carlwgeorge:fedora.im>

18:32:33

let me check with the people that are sensitive about the date and see what they think

<@rcallicotte:fedora.im>

18:32:49

Would lay out the whole process in one page

<@carlwgeorge:fedora.im>

18:33:04

i imagine the response will be something along the lines of "as long as you don't say exactly why you're choosing that date, it's fine"

<@tdawson:fedora.im>

18:35:04

Anything else for Open Floor ?

<@carlwgeorge:fedora.im>

18:35:20

oh i got one more fyi

<@tdawson:fedora.im>

18:35:42

Nobody else has said they have anything, so go for it.

<@carlwgeorge:fedora.im>

18:35:56

bodhi installability checks are sometimes giving false success because testing farm is enabling the buildroot repo

<@tdawson:fedora.im>

18:36:15

Oof

<@carlwgeorge:fedora.im>

18:36:21

examples:

<@carlwgeorge:fedora.im>

18:36:21

- https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7c36fde2dc

<@carlwgeorge:fedora.im>

18:36:21

- https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-3afdcc054d

<@carlwgeorge:fedora.im>

18:36:21

<@rcallicotte:fedora.im>

18:36:42

oh no

<@carlwgeorge:fedora.im>

18:36:46

i don't think this is publicly viewable, but here is the issue tracking the problem https://issues.redhat.com/browse/OSCI-8681

<@rcallicotte:fedora.im>

18:37:27

Yeah I don't have perms to view that issue

<@carlwgeorge:fedora.im>

18:37:55

it's not set as employee-only in the issue, so i think that whole project is set to employee-only

<@tdawson:fedora.im>

18:38:10

Is there a way to test installability before an update makes it to -testing ? I seem to remember Michelle pointing straight at the update repo, but I've never figured out how to do that.

<@carlwgeorge:fedora.im>

18:38:52

<@carlwgeorge:fedora.im>

18:38:52

```

<@carlwgeorge:fedora.im>

18:38:52

```

<@carlwgeorge:fedora.im>

18:38:52

fedpkg mockbuild -- --postinstall

<@carlwgeorge:fedora.im>

18:38:52

i do it when i'm doing local mock builds like this:

<@rcallicotte:fedora.im>

18:39:10

Same

<@tdawson:fedora.im>

18:39:19

Ya ... but I've got a couple hundred packages.

<@carlwgeorge:fedora.im>

18:39:25

<@carlwgeorge:fedora.im>

18:39:25

```

<@carlwgeorge:fedora.im>

18:39:25

fedpkg --release epel10 mockbuild -- --postinstall

<@carlwgeorge:fedora.im>

18:39:25

or if you're building from the rawhide branch prior to requesting the epel10 branch:

<@carlwgeorge:fedora.im>

18:39:25

```

<@nirik:matrix.scrye.com>

18:39:30

The fails to install script does it with dnf repodata

<@carlwgeorge:fedora.im>

18:41:11

yeah that's trickier. not sure what the best way to handle that is. maybe for those big updates always disable auto-push, and only push to stable once you manually verify. that wouldn't fix the problem of doing it before the testing repo, but does help avoid forgetting and things getting promoted to stable after the time or karma threshold.

<@tdawson:fedora.im>

18:42:08

Ya, by default auto-push is disabled, for both karma and time. But the last two I've missed the push to testing by litterally minutes.

<@tdawson:fedora.im>

18:43:00

I'd just like to double check and fix anything before the next push to -testing happens.

<@carlwgeorge:fedora.im>

18:43:35

maybe stage in copr first?

<@tdawson:fedora.im>

18:44:11

I do, but I'd still like to check, because something always sneaks in.

<@tdawson:fedora.im>

18:44:40

Anyway ... if nobody knows without investigating, that's ok.

<@tdawson:fedora.im>

18:47:47

Anything else for Open Floor?

<@tdawson:fedora.im>

18:49:07

I'll take that as a no.

<@tdawson:fedora.im>

18:49:43

Thank you all for coming and the good discussions.

<@tdawson:fedora.im>

18:49:53

And thank you all for all that you do for EPEL and it's community.

<@rcallicotte:fedora.im>

18:50:13

bye Troy Dawson. Thanks!

<@tdawson:fedora.im>

18:50:26

I'll talk to ya'll in two weeks .... next week ya'll get to talk to Carl. ;)

<@nirik:matrix.scrye.com>

18:50:39

Thanks Troy Dawson

<@tdawson:fedora.im>

18:50:46

!endmeeting