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