2025-12-01 16:03:26 <@patrikp:matrix.org> !startmeeting RELENG (2025-12-01)
2025-12-01 16:03:29 <@meetbot:fedora.im> Meeting started at 2025-12-01 16:03:26 UTC
2025-12-01 16:03:29 <@meetbot:fedora.im> The Meeting name is 'RELENG (2025-12-01)'
2025-12-01 16:03:51 <@amedvede:fedora.im> Hello folks
2025-12-01 16:04:01 <@patrikp:matrix.org> !info Agenda is at https://hackmd.io/vm6biLBcTYKtkQUH5kQkmw.
2025-12-01 16:04:01 <@patrikp:matrix.org> !meetingname releng
2025-12-01 16:04:01 <@patrikp:matrix.org> !chair nirik jnsamyak patrikp amedvede
2025-12-01 16:04:01 <@patrikp:matrix.org> !info Meeting is 60 minutes MAX. At the end of 60, it STOPS.
2025-12-01 16:04:04 <@meetbot:fedora.im> The Meeting Name is now releng
2025-12-01 16:04:41 <@patrikp:matrix.org> Hello.
2025-12-01 16:05:10 <@jnsamyak:matrix.org> 0/
2025-12-01 16:05:39 <@amedvede:fedora.im> ✌️
2025-12-01 16:06:21 <@jnsamyak:matrix.org> monday is monday(inggggg)
2025-12-01 16:06:22 <@patrikp:matrix.org> I don't see any upcoming actions and we had the sprint retro/planning earlier today so... Let's take a look at the tracker, maybe?
2025-12-01 16:06:49 <@jnsamyak:matrix.org> Sure, can we do a init? So, to have a F41 EOL'ed cleared out?
2025-12-01 16:06:59 <@patrikp:matrix.org> Yes. 👍️
2025-12-01 16:07:00 <@jnsamyak:matrix.org> Sure, can we do a init first? So, to have a F41 EOL'ed cleared out?
2025-12-01 16:07:07 <@patrikp:matrix.org> !topic Init process.
2025-12-01 16:07:07 <@patrikp:matrix.org> Do we have anything for the init? Any blockers/tasks/issues/requests/features that need releng intervention?
2025-12-01 16:09:18 <@jnsamyak:matrix.org> Okay so F41 EOL is in a mess state right now.
2025-12-01 16:10:52 <@jnsamyak:matrix.org> 1. To be more proactive with the fedora-pgm folks, or keep a check of the schedule so such mess we don't sign ourself into.
2025-12-01 16:10:52 <@jnsamyak:matrix.org> Though there is a schedule discrepency, we have two things in releng to discuss.
2025-12-01 16:10:52 <@jnsamyak:matrix.org> 2. There is a discussion around whether we should do a handoff for the annoucement folks to fedora-pgm folks.
2025-12-01 16:11:43 <@jnsamyak:matrix.org> For the former, I was on PTO that day, I would still recommend folks to sync there calendar with release process if possible to match on timelines.
2025-12-01 16:12:09 <@jnsamyak:matrix.org> I think there is a way in schedule where we can download a ical file and import into our calendars
2025-12-01 16:12:22 <@jnsamyak:matrix.org> But as nirik mentioned
2025-12-01 16:13:15 <@jnsamyak:matrix.org> there are 7/8 places, and most of them are written with different dates, the preferred date/targeted date for EOL now is December 15 which makes sense hence /etc/os-release pointed out to December 15 in machines.
2025-12-01 16:13:44 <@jnsamyak:matrix.org> But now, the next steps would be to send out annoucments one week before the EOL
2025-12-01 16:14:59 <@jnsamyak:matrix.org> which comes me to my second point - I'm happy to have fedora-pgm (one body) to send out emails for such annoucments FPL handles releases final and it would be good from fedora-pgm can handle EOLs etc;
2025-12-01 16:15:16 <@jnsamyak:matrix.org> any query/objections there?
2025-12-01 16:15:25 <@patrikp:matrix.org> I am not against it.
2025-12-01 16:15:58 <@patrikp:matrix.org> Also, the schedules are not in the best shape overall. We have a ticket for it but I think we'll need to collectively go over it and be in agreement.
2025-12-01 16:16:08 <@jnsamyak:matrix.org> Yeah, because i think we as engineers tends to do the hard part but forgets the easiest thing as example of sending email.
2025-12-01 16:17:04 <@jnsamyak:matrix.org> sure, have it in the agenda and bring it to discussion later today in the call or next one, whenever you feel like. I'm mostly talking about the date hiccups today.
2025-12-01 16:17:50 <@patrikp:matrix.org> It raises the question, which place is supposed to be the "single source of truth"? That even PGM/FPL may use in the future.
2025-12-01 16:18:05 <@nirik:matrix.scrye.com> morning folks...
2025-12-01 16:18:27 <@jnsamyak:matrix.org> ALso, For EOLed we need to update repos, bodhi releases etc so everything will be uniform.
2025-12-01 16:18:40 <@jnsamyak:matrix.org> nirik: hey hey, too many calls already :P
2025-12-01 16:18:54 <@nirik:matrix.scrye.com> yes, a source of truth would be good... we don't have one currently really.
2025-12-01 16:19:17 <@nirik:matrix.scrye.com> and changing it all the time is anoying, because it needs a fedora-release package update for the OLD release.
2025-12-01 16:21:03 <@jnsamyak:matrix.org> yeah but for now it is set for dec 15 which is the when we will be doing it, so one less thing to update i think.
2025-12-01 16:21:16 <@jnsamyak:matrix.org> yeah but for now it is set for dec 15 which is when we will be doing it, so one less thing to update i think.
2025-12-01 16:21:44 <@nirik:matrix.scrye.com> yeah, I am for just setting dec 15 this time
2025-12-01 16:21:49 <@nirik:matrix.scrye.com> everywhere
2025-12-01 16:22:06 <@jnsamyak:matrix.org> +1 
2025-12-01 16:22:15 <@jnsamyak:matrix.org> it has been so much of confusion already
2025-12-01 16:22:27 <@jnsamyak:matrix.org> need to clean and close this off nicely before the shutdown;
2025-12-01 16:22:57 <@amedvede:fedora.im> maybe reduce the number of schedules and put everywhere just pointers to the single one will be nice idea
2025-12-01 16:24:08 <@nirik:matrix.scrye.com> less places is probibly a good idea. I don't think the fpm schedules can do pointers tho...
2025-12-01 16:24:40 <@patrikp:matrix.org> I have heard talk about the tool/format of the schedule changing in the future.
2025-12-01 16:25:14 <@patrikp:matrix.org> I haven't heard about Smartsheet before.
2025-12-01 16:25:16 <@jnsamyak:matrix.org> what do you mean by pointers?
2025-12-01 16:25:29 <@jnsamyak:matrix.org> ahhh 
2025-12-01 16:25:30 <@jnsamyak:matrix.org> sorry
2025-12-01 16:25:38 <@jnsamyak:matrix.org> i get what you mean
2025-12-01 16:26:16 <@jnsamyak:matrix.org> Maybe a better way to handle schedule perphaps ;) propose to fesco :P
2025-12-01 16:27:17 <@nirik:matrix.scrye.com> So, in another topic... what is the status of the post release cleanup?
2025-12-01 16:28:06 <@jnsamyak:matrix.org> Good thing - I didn't do the failed compose tracker cleanup since we are moving 
2025-12-01 16:28:27 <@jnsamyak:matrix.org> And, new forge have a way of closing things without making too many noise
2025-12-01 16:29:00 <@nirik:matrix.scrye.com> nice
2025-12-01 16:29:10 <@jnsamyak:matrix.org> Otherwise, the cleanups should be handled this weeks, I saw adrian mentioned that the playbook didn't ran properly
2025-12-01 16:29:38 <@patrikp:matrix.org> Out of curiosity, what do you mean? As in not sending notifications or some such?
2025-12-01 16:29:39 <@jnsamyak:matrix.org> with ptos I didnt get much time to look into that, but it was done from my end, last week; I'll check and close.
2025-12-01 16:30:03 <@jnsamyak:matrix.org> yeahh 
2025-12-01 16:30:25 <@nirik:matrix.scrye.com> I had to add space to the pub volume last week... so would be good to get post release cleanup all done soon.
2025-12-01 16:31:21 <@jnsamyak:matrix.org> Yep the day we migrate the failed-compose repostiory; I'll clean it up; I can do it now also in pagure but it will be 1000s of emails spamming.
2025-12-01 16:31:35 <@jnsamyak:matrix.org> And pagure has no workaround for that sadly
2025-12-01 16:32:15 <@jnsamyak:matrix.org> And, I'll check others too, thanks for the pateince. 
2025-12-01 16:33:22 <@jnsamyak:matrix.org> Anything else?
2025-12-01 16:34:09 <@jnsamyak:matrix.org> One more thing for init, can we move this call an hour earlier or it will be too soon for you nirik ?
2025-12-01 16:34:28 <@jnsamyak:matrix.org> Oh I see your comment on releng
2025-12-01 16:34:32 <@jnsamyak:matrix.org> let it be
2025-12-01 16:34:46 <@nirik:matrix.scrye.com> we could try a whenisgood or whatever for another day?
2025-12-01 16:34:48 <@patrikp:matrix.org> And one more hour before that would be super early morning, right? Since you're on the west coast.
2025-12-01 16:35:02 <@nirik:matrix.scrye.com> yes, 7am... but I already sadly have a meeting then. ;9
2025-12-01 16:35:02 <@patrikp:matrix.org> Good point, it doesn't have to be on Mondays.
2025-12-01 16:35:12 <@jnsamyak:matrix.org> I'll send it out sure.
2025-12-01 16:36:13 <@amedvede:fedora.im> Monday is a good day as it the start of the week, at Tue we have cle meet, so not sure what day will be the best
2025-12-01 16:37:14 <@patrikp:matrix.org> Anything else for the init? Or shall we move straight to tickets?
2025-12-01 16:37:25 <@jnsamyak:matrix.org> happy to move
2025-12-01 16:37:34 <@amedvede:fedora.im> lets move
2025-12-01 16:38:24 <@patrikp:matrix.org> !info This is the time where you can bring up RelEng tickets for discussion, for example if there are blockers, etc.
2025-12-01 16:38:24 <@patrikp:matrix.org> !topic Tickets that need attention.
2025-12-01 16:38:24 <@patrikp:matrix.org> !link https://forge.fedoraproject.org/releng/tickets/issues
2025-12-01 16:38:47 <@patrikp:matrix.org> Yay! The not a bot thumbnail is gone!
2025-12-01 16:39:24 <@patrikp:matrix.org> !releng 13110
2025-12-01 16:39:27 <@zodbot:fedora.im> Issue querying Pagure: Issue not found
2025-12-01 16:39:44 <@patrikp:matrix.org> How can the bot be updated?
2025-12-01 16:39:52 <@jnsamyak:matrix.org> letd go with !link
2025-12-01 16:40:04 <@patrikp:matrix.org> !link https://forge.fedoraproject.org/releng/tickets/issues/13110
2025-12-01 16:42:18 <@patrikp:matrix.org> !link https://forge.fedoraproject.org/releng/tickets/issues/12457
2025-12-01 16:42:18 <@patrikp:matrix.org> Seems like it's not the first time it has happened.
2025-12-01 16:43:14 <@jnsamyak:matrix.org> I see :) (https://forge.fedoraproject.org/releng/tickets/issues/12457#issuecomment-188907)
2025-12-01 16:49:38 <@nirik:matrix.scrye.com> yeah, the thing that doing it manually breaks is that it doesn't get added to koji as a package in that tag
2025-12-01 16:50:12 <@nirik:matrix.scrye.com> so, I am not sure how python-nanobind got fixed.
2025-12-01 16:51:03 <@amedvede:fedora.im> I have checked scm-request-processor toddler plugin and it's not doing enything extra, it just have a checks for branch name and so on
2025-12-01 16:51:09 <@nirik:matrix.scrye.com> oh, right, I think we have a daily script to sync that.
2025-12-01 16:51:20 <@nirik:matrix.scrye.com> yes, the thing that does this runs on bodhi-backend01.
2025-12-01 16:51:23 <@nirik:matrix.scrye.com> Mon Nov 24 23:19:48 2025 package owner kkleine set for python-nanobind in epel10.2 by bodhi [still active]
2025-12-01 16:51:23 <@nirik:matrix.scrye.com> Mon Nov 24 23:19:48 2025 package list entry created: python-nanobind in epel10.2 by bodhi [still active]
2025-12-01 16:52:00 <@patrikp:matrix.org> So all good and can be closed sounds like.
2025-12-01 16:52:03 <@nirik:matrix.scrye.com> fm-consumer@koji_sync_listener.service
2025-12-01 16:52:10 <@nirik:matrix.scrye.com> yeah, +1 to close.
2025-12-01 16:52:35 <@amedvede:fedora.im> +1 looks legit
2025-12-01 16:52:58 <@patrikp:matrix.org> !link https://forge.fedoraproject.org/releng/tickets/issues/13097
2025-12-01 16:53:57 <@patrikp:matrix.org> I don't have autosign permission either but --force works for me probably because of sysadmin-releng FAS membership or some other group.
2025-12-01 16:54:16 <@nirik:matrix.scrye.com> I think he had permissions from back when we had those tags requiring only tag permission (which he has)
2025-12-01 16:54:47 <@nirik:matrix.scrye.com> but I am not sure there's a need to untag the packages. Since they will be blocked, it doesn't matter much...
2025-12-01 16:55:56 <@nirik:matrix.scrye.com> I think I talked to Troy about this before/during the break, but I can't recall the details. ;)
2025-12-01 16:56:13 <@nirik:matrix.scrye.com> so, I'd say ask if he really needs to untag things there?
2025-12-01 16:56:21 <@jnsamyak:matrix.org> sorry Ihad to go lock the door
2025-12-01 16:56:30 <@jnsamyak:matrix.org> sorry I had to go lock the door
2025-12-01 16:57:47 <@patrikp:matrix.org> Alright I posted a comment and time check, 2 mins to go...
2025-12-01 16:57:53 <@patrikp:matrix.org> Any takers for host next week?
2025-12-01 16:58:12 <@amedvede:fedora.im> I can host next week
2025-12-01 16:58:30 <@nirik:matrix.scrye.com> I was gonna ask about the fedora-scm-requests migration to forge... thats going to be tricky to do without disruption. ;(
2025-12-01 16:59:50 <@nirik:matrix.scrye.com> but we can discuss back in the channel since we are out of time. ;)
2025-12-01 17:00:12 <@patrikp:matrix.org> Yup, we're at time.
2025-12-01 17:00:31 <@patrikp:matrix.org> !endmeeting
2025-12-01 17:00:31 <@patrikp:matrix.org> !info Thank you all for coming!