#meeting-3:fedoraproject.org log

<@patrikp:matrix.org>

15:00:17

!startmeeting RELENG (2025-10-13)

<@meetbot:fedora.im>

15:00:21

Meeting started at 2025-10-13 15:00:17 UTC

<@meetbot:fedora.im>

15:00:21

The Meeting name is 'RELENG (2025-10-13)'

<@patrikp:matrix.org>

15:00:36

!info Agenda is at https://hackmd.io/vm6biLBcTYKtkQUH5kQkmw.

<@patrikp:matrix.org>

15:00:36

!meetingname releng

<@patrikp:matrix.org>

15:00:36

!chair nirik jnsamyak patrikp amedvede

<@patrikp:matrix.org>

15:00:36

!info Meeting is 60 minutes MAX. At the end of 60, it STOPS.

<@meetbot:fedora.im>

15:00:39

The Meeting Name is now releng

<@patrikp:matrix.org>

15:02:07

Hello all, I hope your day is going better than mine is. Spent half the day talking to my (new) ISP trying to achieve a very basic thing and made literally no progress whatsoever. I don't know if this is what purgatory feels like but it doesn't feel very good.

<@nirik:matrix.scrye.com>

15:02:20

morning.

<@nirik:matrix.scrye.com>

15:02:24

sorry to hear it. ;(

<@jnsamyak:matrix.org>

15:03:07

hello good morning

<@patrikp:matrix.org>

15:04:40

Alright, init time?

<@patrikp:matrix.org>

15:04:43

!topic Init process.

<@patrikp:matrix.org>

15:04:43

Do we have anything for the init? Any blockers/tasks/issues/requests/features that need releng intervention?

<@jnsamyak:matrix.org>

15:05:00

I have one thing from me!

<@patrikp:matrix.org>

15:05:17

Go for it.

<@jnsamyak:matrix.org>

15:05:37

Migration for releng repository for the new forge!

<@jnsamyak:matrix.org>

15:05:53

nirik: there should be a mail waiting for moderator approval

<@nirik:matrix.scrye.com>

15:05:57

this is going to after release right? or ?

<@jnsamyak:matrix.org>

15:06:06

yes

<@jnsamyak:matrix.org>

15:06:18

But I'm moving things bit by bit

<@jnsamyak:matrix.org>

15:06:20

https://forge.fedoraproject.org/releng

<@jnsamyak:matrix.org>

15:06:38

https://pagure.io/releng/issue/12931#comment-988859

<@nirik:matrix.scrye.com>

15:06:51

hum, so how does that work? changes need to be made both places? or you can sync it at the end?

<@patrikp:matrix.org>

15:06:53

I will be honestly sad to see Pagure go when it happens.

<@jnsamyak:matrix.org>

15:07:10

I'll sync things in the end

<@nirik:matrix.scrye.com>

15:07:23

ok.

<@jnsamyak:matrix.org>

15:07:24

one final time

<@nirik:matrix.scrye.com>

15:07:32

hum, I don't see anything in moderation... to which list?

<@jnsamyak:matrix.org>

15:07:33

i have writtern it in the email

<@jnsamyak:matrix.org>

15:07:42

so everyone is in loop

<@jnsamyak:matrix.org>

15:07:48

should be devel

<@nirik:matrix.scrye.com>

15:08:21

devel-announce?

<@jnsamyak:matrix.org>

15:08:39

devel@lists.fedoraproject.org

<@jnsamyak:matrix.org>

15:08:50

should i do one for devel-annouce as well?

<@nirik:matrix.scrye.com>

15:09:05

devel doesn't need moderation, it should go right thru

<@nirik:matrix.scrye.com>

15:09:28

but I am not seeing it. ;(

<@jnsamyak:matrix.org>

15:09:41

that's what i thought

<@jnsamyak:matrix.org>

15:09:47

i'll resend it

<@jnsamyak:matrix.org>

15:09:51

then sigh

<@amedvede:fedora.im>

15:10:06

Hello folks, sorry I'm late

<@jnsamyak:matrix.org>

15:10:10

maybe because i sent it to test as well in the same email

<@jnsamyak:matrix.org>

15:10:15

it might got bounced

<@jnsamyak:matrix.org>

15:10:20

dunno have happened in past

<@nirik:matrix.scrye.com>

15:10:45

huh, dunno. Happy to help track it... it should give you a bounce if it bounced tho

<@patrikp:matrix.org>

15:11:42

If I understand the comment correctly the filter section in `pungi.rpm.conf.j2` should remain empty (no changes required there) and the changes should only be in `pungi_general.conf`?

<@patrikp:matrix.org>

15:11:42

<@patrikp:matrix.org>

15:11:42

One thing from me for init, for Kevin, very quickly.

<@patrikp:matrix.org>

15:11:42

"But I guess we also need to remove the empty filter in the main one." confuses me slightly.

<@patrikp:matrix.org>

15:11:42

https://pagure.io/fedora-infra/ansible/pull-request/2894#comment-224652

<@patrikp:matrix.org>

15:11:42

<@patrikp:matrix.org>

15:11:42

<@nirik:matrix.scrye.com>

15:12:26

well, I am confused as to why we have the empty one in pungi.rpm.conf.j2 _and_ the one in general...

<@nirik:matrix.scrye.com>

15:12:35

we should only have one I would think?

<@nirik:matrix.scrye.com>

15:13:10

just the one in general I would hope... but perhaps there's some weird reason I can't recall

<@patrikp:matrix.org>

15:13:10

So it means removing the filter line altogether so as to reduce confusion in the future?

<@amedvede:fedora.im>

15:13:31

jnsamyak: do you have some miggration script that do that work, or how migration process is handled?

<@nirik:matrix.scrye.com>

15:13:39

yeah, remove from pungi.rpm.conf.j2 and add the new one in pungi_general.conf...

<@patrikp:matrix.org>

15:14:09

Thanks. Anything else for the init?

<@amedvede:fedora.im>

15:15:01

nothing from me

<@nirik:matrix.scrye.com>

15:15:20

I'm gonna run and feed cats, back in a few.

<@patrikp:matrix.org>

15:15:39

Moving on then.

<@patrikp:matrix.org>

15:15:42

!link https://fedorapeople.org/groups/schedule/f-43/f-43-releng-tasks.html

<@patrikp:matrix.org>

15:15:42

!info Here we list/discuss anything about items that are due to be done in the next week.

<@patrikp:matrix.org>

15:15:42

!topic Scheduled actions coming up in the next week.

<@jnsamyak:matrix.org>

15:16:24

urgent pickup

<@amedvede:fedora.im>

15:18:42

looking to the schedule we have Go/no go meet planned for Thu

<@amedvede:fedora.im>

15:18:55

but there is nothing in my calendar

<@amedvede:fedora.im>

15:19:10

probably need to be added

<@patrikp:matrix.org>

15:20:30

And it happens before the go/no-go, so on the same date regardless of the future go/no-go decision? Shouldn't it only happen after it's GO?

<@patrikp:matrix.org>

15:20:30

Enable Updates in Bodhi for the current release Wed 2025-10-15

<@patrikp:matrix.org>

15:20:30

<@patrikp:matrix.org>

15:20:30

https://docs.fedoraproject.org/en-US/infra/release_guide/sop_final_release/#_bodhi_changes

<@patrikp:matrix.org>

15:20:30

This is the SOP for it?

<@jnsamyak:matrix.org>

15:23:49

it should happen at the time of final release yes

<@patrikp:matrix.org>

15:24:47

So it should be removed from the schedule? Since there it says it's one day BEFORE the go/no-go and it's set there as a separate event. But in reality it's part of the final release process itself which only happens AFTER it's go.

<@jnsamyak:matrix.org>

15:27:17

I think so or club it in with final freeze

<@patrikp:matrix.org>

15:27:21

I'll probably bug you throughout the week with questions about the schedule Samyak as I'm rather confused by it myself.

<@nirik:matrix.scrye.com>

15:27:42

yeah, that only happens after go...

<@patrikp:matrix.org>

15:29:04

You know what, I'll make another hackmd with the proposed schedule structure, that will make it much easier to agree on things and change them before I start opening issues.

<@patrikp:matrix.org>

15:29:32

Otherwise I don't see anything for upcoming actions so... Let's take a look at some tickets?

<@jnsamyak:matrix.org>

15:29:51

yeah

<@jnsamyak:matrix.org>

15:29:58

go ahead

<@patrikp:matrix.org>

15:30:22

!link https://pagure.io/releng/issues

<@patrikp:matrix.org>

15:30:22

!topic Tickets that need attention.

<@patrikp:matrix.org>

15:30:22

!info This is the time where you can bring up releng tickets to discuss if there are blockers, etc.

<@patrikp:matrix.org>

15:30:57

Here's some good news! We are at a respectable 89 open issues which is certainly less than 100+!

<@amedvede:fedora.im>

15:31:17

lets goo

<@nirik:matrix.scrye.com>

15:31:35

I have one item... could be now or open floor.

<@patrikp:matrix.org>

15:31:53

Go for it!

<@nirik:matrix.scrye.com>

15:33:19

we need a fedora-release update for f43. There is already a fedora-repos one... normally we just lump them into one update, but I guess seperate this time. ;)

<@nirik:matrix.scrye.com>

15:33:26

it will need a blocker bug too

<@jnsamyak:matrix.org>

15:34:18

yikes i thought it was dealt?

<@jnsamyak:matrix.org>

15:34:28

Sigh, I'll do it

<@nirik:matrix.scrye.com>

15:35:03

fedora-repos was, not fedora-release. ;) two different packages.

<@jnsamyak:matrix.org>

15:35:33

yeah I remember making changes to both but dealt with one my bad just looked at my changes locally

<@amedvede:fedora.im>

15:35:33

this one? https://src.fedoraproject.org/rpms/fedora-release/

<@jnsamyak:matrix.org>

15:35:39

I'll fix it up

<@nirik:matrix.scrye.com>

15:35:44

also, there was another update to fedora-release sadly... but I guess we just obsolete it and accept the other change.

<@jnsamyak:matrix.org>

15:36:15

yeah the new one with the newer build

<@nirik:matrix.scrye.com>

15:37:47

the reason we need a fedora-release update is to change it's version from 0.x prerelease to x... this determines if the installer says "THIS IS A PRERELEASE" and warns you before installing... or not.

<@nirik:matrix.scrye.com>

15:39:19

thats all I had on that

<@amedvede:fedora.im>

15:41:45

okay, if you don't have anything else, I would like to continue our new tradition of reviewing old ticket

<@amedvede:fedora.im>

15:42:08

!releng 10713

<@zodbot:fedora.im>

15:42:09

<@zodbot:fedora.im>

15:42:09

● **Assignee:** Not Assigned

<@zodbot:fedora.im>

15:42:09

● **Last Updated:** a week ago

<@zodbot:fedora.im>

15:42:09

**releng #10713** (https://pagure.io/releng/issue/10713):**Add ELN to the set of packages to be re-signed at each Branch**

<@zodbot:fedora.im>

15:42:09

● **Opened:** 3 years ago by sgallagh

<@nirik:matrix.scrye.com>

15:43:00

so, we did the docs updates? is there anything else here, or close?

<@amedvede:fedora.im>

15:43:41

I would say close, I think now all eln signed correctly, since it wasn't issue for last few releases

<@amedvede:fedora.im>

15:44:01

mr groomer opinion?

<@jnsamyak:matrix.org>

15:44:16

I think there are doc for it in mass branching section

<@jnsamyak:matrix.org>

15:44:26

lol hey dont quote me

<@patrikp:matrix.org>

15:44:47

https://docs.fedoraproject.org/en-US/infra/release_guide/sop_mass_branching/#_eln_related_work

<@amedvede:fedora.im>

15:44:48

xdd

<@jnsamyak:matrix.org>

15:45:01

close!

<@amedvede:fedora.im>

15:45:20

next one

<@amedvede:fedora.im>

15:45:30

!releng 11233

<@zodbot:fedora.im>

15:45:31

**releng #11233** (https://pagure.io/releng/issue/11233):**Automation of request-repos in flatpaks namespace**

<@zodbot:fedora.im>

15:45:31

<@zodbot:fedora.im>

15:45:31

● **Opened:** 2 years ago by yselkowitz

<@zodbot:fedora.im>

15:45:31

● **Last Updated:** a week ago

<@zodbot:fedora.im>

15:45:31

● **Assignee:** Not Assigned

<@patrikp:matrix.org>

15:46:17

Ideally when we close these we should add context to the comment, so I'd say confirm that it's been added to the docs, link to the relevant SOP section, and only then close.

<@jnsamyak:matrix.org>

15:46:29

ofcourse!

<@nirik:matrix.scrye.com>

15:46:44

so I guess what we could do here is enhance the toddler to just process these if the submitter is in the right group...

<@jnsamyak:matrix.org>

15:47:20

We have brought it up in the past, but I guess we should wait now till the new migration happens and see if we can leverage forgejo actions with that

<@nirik:matrix.scrye.com>

15:48:09

well, we have a toddler that processes these already. It would just need to be adjusted to also process these (with some new checks)

<@amedvede:fedora.im>

15:49:03

yeah

<@amedvede:fedora.im>

15:49:29

after the move to new forge I can take a look on it since I added check in request-repo toddler previously

<@jnsamyak:matrix.org>

15:49:47

that's true

<@amedvede:fedora.im>

15:49:49

lets just keep it in a backlog for now

<@jnsamyak:matrix.org>

15:49:57

sure

<@amedvede:fedora.im>

15:50:34

last one if we still have time

<@amedvede:fedora.im>

15:50:43

!releng 11099

<@zodbot:fedora.im>

15:50:44

● **Opened:** 2 years ago by adamwill

<@zodbot:fedora.im>

15:50:44

<@zodbot:fedora.im>

15:50:44

**releng #11099** (https://pagure.io/releng/issue/11099):**IoT composes consistently embedding older ostrees in the installer image**

<@zodbot:fedora.im>

15:50:44

● **Last Updated:** 2 years ago

<@zodbot:fedora.im>

15:50:44

● **Assignee:** Not Assigned

<@jnsamyak:matrix.org>

15:52:09

I see theproblem was there in last comment, perphaps needs investigation?

<@jnsamyak:matrix.org>

15:52:50

step 1 should be to find out if ithis is still happening

<@nirik:matrix.scrye.com>

15:52:54

I'm really not sure about this one at all. ;)

<@nirik:matrix.scrye.com>

15:52:59

yeah. +1

<@jnsamyak:matrix.org>

15:53:04

step 2 if not close, if yes look for possible solution

<@amedvede:fedora.im>

15:53:18

good ticket to mark as "planned work ticket" for some of us

<@jnsamyak:matrix.org>

15:53:41

sure add a groomed tag to it, and pick it up if you like

<@jnsamyak:matrix.org>

15:53:45

also time check

<@patrikp:matrix.org>

15:54:16

Any takers for next week's host?

<@amedvede:fedora.im>

15:54:31

I can take it

<@jnsamyak:matrix.org>

15:54:38

I'm off next week because of diwali \0/

<@amedvede:fedora.im>

15:54:43

or rock paper scissors?

<@amedvede:fedora.im>

15:54:57

oh okay

<@amedvede:fedora.im>

15:55:01

I'll take

<@patrikp:matrix.org>

15:55:07

I think we can sort out one more very quickly.

<@patrikp:matrix.org>

15:55:12

!releng 13007

<@zodbot:fedora.im>

15:55:13

● **Opened:** a day ago by rominf

<@zodbot:fedora.im>

15:55:13

● **Last Updated:** a day ago

<@zodbot:fedora.im>

15:55:13

**releng #13007** (https://pagure.io/releng/issue/13007):**Amend last commit in python-exoscale repo, branch 43**

<@zodbot:fedora.im>

15:55:13

<@zodbot:fedora.im>

15:55:13

● **Assignee:** Not Assigned

<@nirik:matrix.scrye.com>

15:55:32

yeah, we don't do this normally.

<@patrikp:matrix.org>

15:55:36

I would say just close it as won't fix and link to the FESCo policy about messing with git history if someone happens to have it.

<@nirik:matrix.scrye.com>

15:55:38

they should just push another commit

<@patrikp:matrix.org>

15:55:46

Unless there's a super good reason we don't do that.

<@patrikp:matrix.org>

15:55:57

Yup. Is the policy somewhere in the docs?

<@patrikp:matrix.org>

15:56:12

I think it may have been some Fedora discussion last time we talked about it but honestly not sure.

<@nirik:matrix.scrye.com>

15:57:15

not sure where it is.

<@patrikp:matrix.org>

15:58:39

!topic Choose next chair.

<@patrikp:matrix.org>

15:58:39

!info Next chair October 20th: Anton

<@patrikp:matrix.org>

15:58:45

Alright, and we're nearly at time here.

<@patrikp:matrix.org>

15:58:58

Back to bickering with the ISP I go. 🤮

<@patrikp:matrix.org>

15:59:21

!endmeeting

<@patrikp:matrix.org>

15:59:21

!info Thank you all for coming!