2025-10-13 15:00:17 <@patrikp:matrix.org> !startmeeting RELENG (2025-10-13)
2025-10-13 15:00:21 <@meetbot:fedora.im> Meeting started at 2025-10-13 15:00:17 UTC
2025-10-13 15:00:21 <@meetbot:fedora.im> The Meeting name is 'RELENG (2025-10-13)'
2025-10-13 15:00:36 <@patrikp:matrix.org> !info Agenda is at https://hackmd.io/vm6biLBcTYKtkQUH5kQkmw.
2025-10-13 15:00:36 <@patrikp:matrix.org> !meetingname releng
2025-10-13 15:00:36 <@patrikp:matrix.org> !chair nirik jnsamyak patrikp amedvede
2025-10-13 15:00:36 <@patrikp:matrix.org> !info Meeting is 60 minutes MAX. At the end of 60, it STOPS.
2025-10-13 15:00:39 <@meetbot:fedora.im> The Meeting Name is now releng
2025-10-13 15:02:07 <@patrikp:matrix.org> 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.
2025-10-13 15:02:20 <@nirik:matrix.scrye.com> morning.
2025-10-13 15:02:24 <@nirik:matrix.scrye.com> sorry to hear it. ;(
2025-10-13 15:03:07 <@jnsamyak:matrix.org> hello good morning
2025-10-13 15:04:40 <@patrikp:matrix.org> Alright, init time?
2025-10-13 15:04:43 <@patrikp:matrix.org> !topic Init process.
2025-10-13 15:04:43 <@patrikp:matrix.org> Do we have anything for the init? Any blockers/tasks/issues/requests/features that need releng intervention?
2025-10-13 15:05:00 <@jnsamyak:matrix.org> I have one thing from me!
2025-10-13 15:05:17 <@patrikp:matrix.org> Go for it.
2025-10-13 15:05:37 <@jnsamyak:matrix.org> Migration for releng repository for the new forge!
2025-10-13 15:05:53 <@jnsamyak:matrix.org> nirik: there should be a mail waiting for moderator approval
2025-10-13 15:05:57 <@nirik:matrix.scrye.com> this is going to after release right? or ?
2025-10-13 15:06:06 <@jnsamyak:matrix.org> yes
2025-10-13 15:06:18 <@jnsamyak:matrix.org> But I'm moving things bit by bit
2025-10-13 15:06:20 <@jnsamyak:matrix.org> https://forge.fedoraproject.org/releng
2025-10-13 15:06:38 <@jnsamyak:matrix.org> https://pagure.io/releng/issue/12931#comment-988859
2025-10-13 15:06:51 <@nirik:matrix.scrye.com> hum, so how does that work? changes need to be made both places? or you can sync it at the end?
2025-10-13 15:06:53 <@patrikp:matrix.org> I will be honestly sad to see Pagure go when it happens.
2025-10-13 15:07:10 <@jnsamyak:matrix.org> I'll sync things in the end
2025-10-13 15:07:23 <@nirik:matrix.scrye.com> ok.
2025-10-13 15:07:24 <@jnsamyak:matrix.org> one final time
2025-10-13 15:07:32 <@nirik:matrix.scrye.com> hum, I don't see anything in moderation... to which list?
2025-10-13 15:07:33 <@jnsamyak:matrix.org> i have writtern it in the email
2025-10-13 15:07:42 <@jnsamyak:matrix.org> so everyone is in loop
2025-10-13 15:07:48 <@jnsamyak:matrix.org> should be devel
2025-10-13 15:08:21 <@nirik:matrix.scrye.com> devel-announce?
2025-10-13 15:08:39 <@jnsamyak:matrix.org> devel@lists.fedoraproject.org
2025-10-13 15:08:50 <@jnsamyak:matrix.org> should i do one for devel-annouce as well?
2025-10-13 15:09:05 <@nirik:matrix.scrye.com> devel doesn't need moderation, it should go right thru
2025-10-13 15:09:28 <@nirik:matrix.scrye.com> but I am not seeing it. ;(
2025-10-13 15:09:41 <@jnsamyak:matrix.org> that's what i thought
2025-10-13 15:09:47 <@jnsamyak:matrix.org> i'll resend it
2025-10-13 15:09:51 <@jnsamyak:matrix.org> then sigh 
2025-10-13 15:10:06 <@amedvede:fedora.im> Hello folks, sorry I'm late
2025-10-13 15:10:10 <@jnsamyak:matrix.org> maybe because i sent it to test as well in the same email
2025-10-13 15:10:15 <@jnsamyak:matrix.org> it might got bounced
2025-10-13 15:10:20 <@jnsamyak:matrix.org> dunno have happened in past
2025-10-13 15:10:45 <@nirik:matrix.scrye.com> huh, dunno. Happy to help track it... it should give you a bounce if it bounced tho
2025-10-13 15:11:42 <@patrikp:matrix.org> 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`?
2025-10-13 15:11:42 <@patrikp:matrix.org> 
2025-10-13 15:11:42 <@patrikp:matrix.org> One thing from me for init, for Kevin, very quickly.
2025-10-13 15:11:42 <@patrikp:matrix.org> "But I guess we also need to remove the empty filter in the main one." confuses me slightly.
2025-10-13 15:11:42 <@patrikp:matrix.org> https://pagure.io/fedora-infra/ansible/pull-request/2894#comment-224652
2025-10-13 15:11:42 <@patrikp:matrix.org> 
2025-10-13 15:11:42 <@patrikp:matrix.org> 
2025-10-13 15:12:26 <@nirik:matrix.scrye.com> well, I am confused as to why we have the empty one in pungi.rpm.conf.j2 _and_ the one in general...
2025-10-13 15:12:35 <@nirik:matrix.scrye.com> we should only have one I would think?
2025-10-13 15:13:10 <@nirik:matrix.scrye.com> just the one in general I would hope... but perhaps there's some weird reason I can't recall
2025-10-13 15:13:10 <@patrikp:matrix.org> So it means removing the filter line altogether so as to reduce confusion in the future?
2025-10-13 15:13:31 <@amedvede:fedora.im> jnsamyak: do you have some miggration script that do that work, or how migration process is handled?
2025-10-13 15:13:39 <@nirik:matrix.scrye.com> yeah, remove from pungi.rpm.conf.j2 and add the new one in pungi_general.conf...
2025-10-13 15:14:09 <@patrikp:matrix.org> Thanks. Anything else for the init?
2025-10-13 15:15:01 <@amedvede:fedora.im> nothing from me
2025-10-13 15:15:20 <@nirik:matrix.scrye.com> I'm gonna run and feed cats, back in a few.
2025-10-13 15:15:39 <@patrikp:matrix.org> Moving on then.
2025-10-13 15:15:42 <@patrikp:matrix.org> !link https://fedorapeople.org/groups/schedule/f-43/f-43-releng-tasks.html
2025-10-13 15:15:42 <@patrikp:matrix.org> !info Here we list/discuss anything about items that are due to be done in the next week.
2025-10-13 15:15:42 <@patrikp:matrix.org> !topic Scheduled actions coming up in the next week.
2025-10-13 15:16:24 <@jnsamyak:matrix.org> urgent pickup
2025-10-13 15:18:42 <@amedvede:fedora.im> looking to the schedule we have Go/no go meet planned for Thu
2025-10-13 15:18:55 <@amedvede:fedora.im> but there is nothing in my calendar
2025-10-13 15:19:10 <@amedvede:fedora.im> probably need to be added
2025-10-13 15:20:30 <@patrikp:matrix.org> 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?
2025-10-13 15:20:30 <@patrikp:matrix.org> Enable Updates in Bodhi for the current release	Wed 2025-10-15
2025-10-13 15:20:30 <@patrikp:matrix.org> 
2025-10-13 15:20:30 <@patrikp:matrix.org> https://docs.fedoraproject.org/en-US/infra/release_guide/sop_final_release/#_bodhi_changes
2025-10-13 15:20:30 <@patrikp:matrix.org> This is the SOP for it?
2025-10-13 15:23:49 <@jnsamyak:matrix.org> it should happen at the time of final release yes
2025-10-13 15:24:47 <@patrikp:matrix.org> 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.
2025-10-13 15:27:17 <@jnsamyak:matrix.org> I think so or club it in with final freeze
2025-10-13 15:27:21 <@patrikp:matrix.org> I'll probably bug you throughout the week with questions about the schedule Samyak as I'm rather confused by it myself.
2025-10-13 15:27:42 <@nirik:matrix.scrye.com> yeah, that only happens after go...
2025-10-13 15:29:04 <@patrikp:matrix.org> 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.
2025-10-13 15:29:32 <@patrikp:matrix.org> Otherwise I don't see anything for upcoming actions so... Let's take a look at some tickets?
2025-10-13 15:29:51 <@jnsamyak:matrix.org> yeah
2025-10-13 15:29:58 <@jnsamyak:matrix.org> go ahead
2025-10-13 15:30:22 <@patrikp:matrix.org> !link https://pagure.io/releng/issues
2025-10-13 15:30:22 <@patrikp:matrix.org> !topic Tickets that need attention.
2025-10-13 15:30:22 <@patrikp:matrix.org> !info This is the time where you can bring up releng tickets to discuss if there are blockers, etc.
2025-10-13 15:30:57 <@patrikp:matrix.org> Here's some good news! We are at a respectable 89 open issues which is certainly less than 100+!
2025-10-13 15:31:17 <@amedvede:fedora.im> lets goo
2025-10-13 15:31:35 <@nirik:matrix.scrye.com> I have one item... could be now or open floor.
2025-10-13 15:31:53 <@patrikp:matrix.org> Go for it!
2025-10-13 15:33:19 <@nirik:matrix.scrye.com> 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. ;)
2025-10-13 15:33:26 <@nirik:matrix.scrye.com> it will need a blocker bug too
2025-10-13 15:34:18 <@jnsamyak:matrix.org> yikes i thought it was dealt?
2025-10-13 15:34:28 <@jnsamyak:matrix.org> Sigh, I'll do it
2025-10-13 15:35:03 <@nirik:matrix.scrye.com> fedora-repos was, not fedora-release. ;) two different packages.
2025-10-13 15:35:33 <@jnsamyak:matrix.org> yeah I remember making changes to both but dealt with one my bad just looked at my changes locally
2025-10-13 15:35:33 <@amedvede:fedora.im> this one? https://src.fedoraproject.org/rpms/fedora-release/
2025-10-13 15:35:39 <@jnsamyak:matrix.org> I'll fix it up
2025-10-13 15:35:44 <@nirik:matrix.scrye.com> also, there was another update to fedora-release sadly... but I guess we just obsolete it and accept the other change.
2025-10-13 15:36:15 <@jnsamyak:matrix.org> yeah the new one with the newer build
2025-10-13 15:37:47 <@nirik:matrix.scrye.com> 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.
2025-10-13 15:39:19 <@nirik:matrix.scrye.com> thats all I had on that
2025-10-13 15:41:45 <@amedvede:fedora.im> okay, if you don't have anything else, I would like to continue our new tradition of reviewing old ticket
2025-10-13 15:42:08 <@amedvede:fedora.im> !releng 10713
2025-10-13 15:42:09 <@zodbot:fedora.im> 
2025-10-13 15:42:09 <@zodbot:fedora.im> ● **Assignee:** Not Assigned
2025-10-13 15:42:09 <@zodbot:fedora.im> ● **Last Updated:** a week ago
2025-10-13 15:42:09 <@zodbot:fedora.im> **releng #10713** (https://pagure.io/releng/issue/10713):**Add ELN to the set of packages to be re-signed at each Branch**
2025-10-13 15:42:09 <@zodbot:fedora.im> ● **Opened:** 3 years ago by sgallagh
2025-10-13 15:43:00 <@nirik:matrix.scrye.com> so, we did the docs updates? is there anything else here, or close?
2025-10-13 15:43:41 <@amedvede:fedora.im> I would say close, I think now all eln signed correctly, since it wasn't issue for last few releases
2025-10-13 15:44:01 <@amedvede:fedora.im> mr groomer opinion?
2025-10-13 15:44:16 <@jnsamyak:matrix.org> I think there are doc for it in mass branching section
2025-10-13 15:44:26 <@jnsamyak:matrix.org> lol hey dont quote me
2025-10-13 15:44:47 <@patrikp:matrix.org> https://docs.fedoraproject.org/en-US/infra/release_guide/sop_mass_branching/#_eln_related_work
2025-10-13 15:44:48 <@amedvede:fedora.im> xdd
2025-10-13 15:45:01 <@jnsamyak:matrix.org> close!
2025-10-13 15:45:20 <@amedvede:fedora.im> next one
2025-10-13 15:45:30 <@amedvede:fedora.im> !releng 11233
2025-10-13 15:45:31 <@zodbot:fedora.im> **releng #11233** (https://pagure.io/releng/issue/11233):**Automation of request-repos in flatpaks namespace**
2025-10-13 15:45:31 <@zodbot:fedora.im> 
2025-10-13 15:45:31 <@zodbot:fedora.im> ● **Opened:** 2 years ago by yselkowitz
2025-10-13 15:45:31 <@zodbot:fedora.im> ● **Last Updated:** a week ago
2025-10-13 15:45:31 <@zodbot:fedora.im> ● **Assignee:** Not Assigned
2025-10-13 15:46:17 <@patrikp:matrix.org> 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.
2025-10-13 15:46:29 <@jnsamyak:matrix.org> ofcourse!
2025-10-13 15:46:44 <@nirik:matrix.scrye.com> so I guess what we could do here is enhance the toddler to just process these if the submitter is in the right group...
2025-10-13 15:47:20 <@jnsamyak:matrix.org> 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
2025-10-13 15:48:09 <@nirik:matrix.scrye.com> well, we have a toddler that processes these already. It would just need to be adjusted to also process these (with some new checks)
2025-10-13 15:49:03 <@amedvede:fedora.im> yeah
2025-10-13 15:49:29 <@amedvede:fedora.im> after the move to new forge I can take a look on it since I added check in request-repo toddler previously
2025-10-13 15:49:47 <@jnsamyak:matrix.org> that's true 
2025-10-13 15:49:49 <@amedvede:fedora.im> lets just keep it in a backlog for now
2025-10-13 15:49:57 <@jnsamyak:matrix.org> sure
2025-10-13 15:50:34 <@amedvede:fedora.im> last one if we still have time
2025-10-13 15:50:43 <@amedvede:fedora.im> !releng 11099
2025-10-13 15:50:44 <@zodbot:fedora.im> ● **Opened:** 2 years ago by adamwill
2025-10-13 15:50:44 <@zodbot:fedora.im> 
2025-10-13 15:50:44 <@zodbot:fedora.im> **releng #11099** (https://pagure.io/releng/issue/11099):**IoT composes consistently embedding older ostrees in the installer image**
2025-10-13 15:50:44 <@zodbot:fedora.im> ● **Last Updated:** 2 years ago
2025-10-13 15:50:44 <@zodbot:fedora.im> ● **Assignee:** Not Assigned
2025-10-13 15:52:09 <@jnsamyak:matrix.org> I see theproblem was there in last comment, perphaps needs investigation?
2025-10-13 15:52:50 <@jnsamyak:matrix.org> step 1 should be to find out if ithis is still happening
2025-10-13 15:52:54 <@nirik:matrix.scrye.com> I'm really not sure about this one at all. ;)
2025-10-13 15:52:59 <@nirik:matrix.scrye.com> yeah. +1
2025-10-13 15:53:04 <@jnsamyak:matrix.org> step 2 if not close, if yes look for possible solution
2025-10-13 15:53:18 <@amedvede:fedora.im> good ticket to mark as "planned work ticket" for some of us
2025-10-13 15:53:41 <@jnsamyak:matrix.org> sure add a groomed tag to it, and pick it up if you like
2025-10-13 15:53:45 <@jnsamyak:matrix.org> also time check
2025-10-13 15:54:16 <@patrikp:matrix.org> Any takers for next week's host?
2025-10-13 15:54:31 <@amedvede:fedora.im> I can take it
2025-10-13 15:54:38 <@jnsamyak:matrix.org> I'm off next week because of diwali \0/
2025-10-13 15:54:43 <@amedvede:fedora.im> or rock paper scissors?
2025-10-13 15:54:57 <@amedvede:fedora.im> oh okay
2025-10-13 15:55:01 <@amedvede:fedora.im> I'll take
2025-10-13 15:55:07 <@patrikp:matrix.org> I think we can sort out one more very quickly.
2025-10-13 15:55:12 <@patrikp:matrix.org> !releng 13007
2025-10-13 15:55:13 <@zodbot:fedora.im> ● **Opened:** a day ago by rominf
2025-10-13 15:55:13 <@zodbot:fedora.im> ● **Last Updated:** a day ago
2025-10-13 15:55:13 <@zodbot:fedora.im> **releng #13007** (https://pagure.io/releng/issue/13007):**Amend last commit in python-exoscale repo, branch 43**
2025-10-13 15:55:13 <@zodbot:fedora.im> 
2025-10-13 15:55:13 <@zodbot:fedora.im> ● **Assignee:** Not Assigned
2025-10-13 15:55:32 <@nirik:matrix.scrye.com> yeah, we don't do this normally.
2025-10-13 15:55:36 <@patrikp:matrix.org> 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.
2025-10-13 15:55:38 <@nirik:matrix.scrye.com> they should just push another commit
2025-10-13 15:55:46 <@patrikp:matrix.org> Unless there's a super good reason we don't do that.
2025-10-13 15:55:57 <@patrikp:matrix.org> Yup. Is the policy somewhere in the docs?
2025-10-13 15:56:12 <@patrikp:matrix.org> I think it may have been some Fedora discussion last time we talked about it but honestly not sure.
2025-10-13 15:57:15 <@nirik:matrix.scrye.com> not sure where it is.
2025-10-13 15:58:39 <@patrikp:matrix.org> !topic Choose next chair.
2025-10-13 15:58:39 <@patrikp:matrix.org> !info Next chair October 20th: Anton
2025-10-13 15:58:45 <@patrikp:matrix.org> Alright, and we're nearly at time here.
2025-10-13 15:58:58 <@patrikp:matrix.org> Back to bickering with the ISP I go. 🤮
2025-10-13 15:59:21 <@patrikp:matrix.org> !endmeeting
2025-10-13 15:59:21 <@patrikp:matrix.org> !info Thank you all for coming!