<@meetbot:fedora.im>
08:38:05
Text Minutes: https://meetbot.fedoraproject.org/meeting-3_matrix_fedoraproject-org/2025-06-23/cpe-infra-releng-daily-standup.2025-06-23-08.15.txt
<@patrikp:matrix.org>
15:00:05
!startmeeting RELENG (2025-06-23)
<@meetbot:fedora.im>
15:00:08
Meeting started at 2025-06-23 15:00:05 UTC
<@meetbot:fedora.im>
15:00:09
The Meeting name is 'RELENG (2025-06-23)'
<@patrikp:matrix.org>
15:00:14
!info Agenda is at https://hackmd.io/vm6biLBcTYKtkQUH5kQkmw.
<@patrikp:matrix.org>
15:00:14
!info Meeting is 60 minutes MAX. At the end of 60, it stops.
<@patrikp:matrix.org>
15:00:14
!chair nirik jnsamyak patrikp amedvede
<@patrikp:matrix.org>
15:00:14
!meetingname releng
<@meetbot:fedora.im>
15:00:16
The Meeting Name is now releng
<@jnsamyak:matrix.org>
15:00:27
0/
<@patrikp:matrix.org>
15:00:29
Hello.
<@nirik:matrix.scrye.com>
15:00:40
👋
<@jnsamyak:matrix.org>
15:00:43
Hellow how is everyone??
<@patrikp:matrix.org>
15:01:00
Hot. Very hot.
<@patrikp:matrix.org>
15:01:37
Init time?
<@jnsamyak:matrix.org>
15:01:50
Long time no see folks, I finally arrived India last weekend, the flight got cancelled it was a mess but all sorted I’m home and finally I can sleep in my bed
<@patrikp:matrix.org>
15:02:23
International travel is so stressful, well done guys. You physically manifested yourselves on a different continent, no easy task.
<@jnsamyak:matrix.org>
15:02:43
Hehe
<@jnsamyak:matrix.org>
15:02:52
Anyways how’s releng going? I see tracker is above 100 again :3
<@patrikp:matrix.org>
15:03:11
Do we have anything for the init? Any blockers/tasks/issues/requests/features that need releng intervention?
<@patrikp:matrix.org>
15:03:11
!topic Init process.
<@patrikp:matrix.org>
15:03:20
Let me get this thing out of the way first then we can go to tickets.
<@jnsamyak:matrix.org>
15:04:18
Shoooot
<@patrikp:matrix.org>
15:04:43
<@patrikp:matrix.org>
15:04:43
OpenH264:
<@patrikp:matrix.org>
15:04:43
It's looking really good. Soon we will be able to close the ticket I think. All I want to do is to finish the SOP before closing.
<@patrikp:matrix.org>
15:04:43
<@patrikp:matrix.org>
15:04:43
What steps had to be done after the ones I did? And was it a one time thing or will they have to be repeated every time?
<@patrikp:matrix.org>
15:04:43
https://pagure.io/releng/issue/12617#comment-976377
<@patrikp:matrix.org>
15:05:16
"I moved the old os/ dirs aside and @adrian was nice enough to fix the db and trigger a re-read."
<@jnsamyak:matrix.org>
15:05:34
Every time we get a request we process it basically and this SOP should be used
<@patrikp:matrix.org>
15:05:39
Could this be described in more detail if possible, please? It doesn't have to be right now either, ticket is good.
<@patrikp:matrix.org>
15:05:48
You're missing the point of my question.
<@jnsamyak:matrix.org>
15:06:09
Check the old SOP I think there was a point to sync it to syndries also
<@jnsamyak:matrix.org>
15:06:12
Nit sure
<@nirik:matrix.scrye.com>
15:06:45
The directory / tree structure was different from the old ODCS compose vs the koji dist-repo compose .
<@jnsamyak:matrix.org>
15:06:55
Please close the ticket sop should be handled separately
<@nirik:matrix.scrye.com>
15:06:57
the odcs one had a os/ directory in it, the new one doesn't.
<@nirik:matrix.scrye.com>
15:07:23
so both of those were there and confused mirrormanager. ;) Adrain cleared it in the db and had it redetect it.
<@nirik:matrix.scrye.com>
15:07:28
we should be all good going foward now.
<@patrikp:matrix.org>
15:07:50
So all that needs to be done is to sync the repodata? And the SOP ends there?
<@patrikp:matrix.org>
15:08:49
Sounds good to me if so. I'll close the ticket and clean up the SOP and send for final review. That's all from me on this topic. Scheduled actions? Or anyone else has something?
<@nirik:matrix.scrye.com>
15:09:19
yep. I think so
<@jnsamyak:matrix.org>
15:09:24
Nothing from me
<@patrikp:matrix.org>
15:09:43
!topic Scheduled actions coming up in the next week.
<@patrikp:matrix.org>
15:09:43
!link https://fedorapeople.org/groups/schedule/f-43/f-43-releng-tasks.html
<@patrikp:matrix.org>
15:09:43
!link https://fedorapeople.org/groups/schedule/f-42/f-42-releng-tasks.html
<@patrikp:matrix.org>
15:09:43
!info Here we list/discuss anything about items that are due to be done in the next week.
<@jnsamyak:matrix.org>
15:10:22
This reminds me
<@nirik:matrix.scrye.com>
15:10:45
The dc move is coming up. ;) But thats not really a releng thing...
<@jnsamyak:matrix.org>
15:10:47
FOR CLEANUPS for eol we need to actually re,ove modular from the db
<@jnsamyak:matrix.org>
15:11:11
In order to have the move to archive playbook run
<@nirik:matrix.scrye.com>
15:11:19
There may be an issue with ppc64le composes related to the dc move tho. Turns out the virt layering we want to do doesn't work the way I thought it did. ;(
<@jnsamyak:matrix.org>
15:11:20
I can check more on that tomorrow
<@jnsamyak:matrix.org>
15:11:33
But it was failing on that
<@jnsamyak:matrix.org>
15:11:51
:3
<@nirik:matrix.scrye.com>
15:12:34
exploring options. At worse case we will have to make them failable for a week or so and then resume on power9s for them for short term
<@patrikp:matrix.org>
15:12:52
<@patrikp:matrix.org>
15:12:52
But I wanted to bring up a larger point. I was looking for an SOP for this and couldn't find it.
<@patrikp:matrix.org>
15:12:52
<@patrikp:matrix.org>
15:12:52
I think each milestone/thing in the calendar should be a hyperlink to an SOP that has the same title as is in the calendar to make things less confusing and more clear.
<@patrikp:matrix.org>
15:12:52
Retire packages with security issues Mon 2025-06-30
<@patrikp:matrix.org>
15:12:52
Next thing I see in relation to F43 is:
<@jnsamyak:matrix.org>
15:12:53
Hmmm
<@patrikp:matrix.org>
15:13:25
Is the retirement a simple thing? Running a script or some such? Just wanted to point out that it's also supposed to happen next week.
<@patrikp:matrix.org>
15:14:20
And since all 3 of us are talking about completely different things maybe we take those one at a time.
<@nirik:matrix.scrye.com>
15:14:26
it was a long topic for discussion...
<@nirik:matrix.scrye.com>
15:14:40
someone proposed we do this, fesco said 'sure' and releng said... '
<@nirik:matrix.scrye.com>
15:14:57
ok, but not us, we have no capacity, someone else will need to do it'
<@nirik:matrix.scrye.com>
15:14:59
and no one has
<@patrikp:matrix.org>
15:15:14
This is in relation to improving documentation?
<@nirik:matrix.scrye.com>
15:15:16
yeah, happy to do one topic at a time. ;)
<@patrikp:matrix.org>
15:15:22
Or what was the proposed thing?
<@nirik:matrix.scrye.com>
15:15:27
no, the secureity issues retirement
<@jnsamyak:matrix.org>
15:15:38
This is something miro usually handles it
<@jnsamyak:matrix.org>
15:15:43
But we can check
<@patrikp:matrix.org>
15:15:53
Shouldn't it be in a different category than releng then?
<@patrikp:matrix.org>
15:16:04
If that turns out to be the case and we don't actually do it.
<@patrikp:matrix.org>
15:16:38
Or "group" I think is the lingo of the schedule. It shows up when you filter by clicking on releng.
<@nirik:matrix.scrye.com>
15:16:58
no, you are thinking of retiring packages with broken deps
<@nirik:matrix.scrye.com>
15:17:21
to my understanding no one at all is working on 'retire packages with security issues'
<@patrikp:matrix.org>
15:17:49
Which piece of the infrastructure checks for the security issues? Or how would we get the list of things that need to be retired due to security issues?
<@patrikp:matrix.org>
15:17:57
It's some CI in Bodhi?
<@nirik:matrix.scrye.com>
15:18:19
no, nothing exists. Let me find the orig proposal
<@patrikp:matrix.org>
15:18:28
Ah, got you. This was a proposed thing and the schedule is outdated.
<@nirik:matrix.scrye.com>
15:19:10
https://pagure.io/fesco/issue/1935
<@nirik:matrix.scrye.com>
15:19:46
so this would require an actual process, etc.
<@patrikp:matrix.org>
15:21:48
Doesn't this sound more like a QA thing if I may ask an earnest question?
<@patrikp:matrix.org>
15:23:14
Last reply over 5 years ago, dang. So... Do we remove it from the schedule? I see counterarguments in the mailing list too.
<@patrikp:matrix.org>
15:23:43
In any case it doesn't sound like we'll be doing it next Monday. 😆
<@patrikp:matrix.org>
15:24:32
In that case the other upcoming action is a month away from now so we can move to another point that was raised.
<@nirik:matrix.scrye.com>
15:24:52
yeah, definitely not doing it monday... but we could reopen figuring it out I guess.
<@nirik:matrix.scrye.com>
15:25:04
next action should be mass rebuild ?
<@patrikp:matrix.org>
15:25:11
What do you think about my idea of hyperlinks in the schedule?
<@patrikp:matrix.org>
15:25:32
This one could be a link to the Fesco ticket. Because right now it's not clear at all that we don't actually do it.
<@patrikp:matrix.org>
15:26:13
But the hyperlinks in general. If each calendar event linked to exactly one SOP where it's detailed in as much detail as possible, even with context (why it's important, how it fits into the infra, etc).
<@patrikp:matrix.org>
15:27:18
I have a goal in workday about docs so I'm wondering if I'm heading in the right direction or if I'm way off base and wasting time.
<@patrikp:matrix.org>
15:28:19
F43 cycle would be a really good time to streamline docs IMHO.
<@nirik:matrix.scrye.com>
15:29:07
always good to improve docs.
<@patrikp:matrix.org>
15:29:35
Alright. That's all the questions I had for now. Do you want to talk more about some of the things you brought up?
<@jnsamyak:matrix.org>
15:30:53
I have to drop for dinner, I’ll look for mom or just tag me if there is an action item on me
<@jnsamyak:matrix.org>
15:31:00
See you all 0/
<@nirik:matrix.scrye.com>
15:33:44
either way, need to go feed cats, back in ~10ish
<@patrikp:matrix.org>
15:38:35
I suppose you'll talk more about the DC move during the call later. Soo... Tickets, once you come back?
<@patrikp:matrix.org>
15:38:41
!topic Tickets that need attention.
<@patrikp:matrix.org>
15:38:41
!info This is the time where you can bring up releng tickets to discuss if there are blockers, etc.
<@patrikp:matrix.org>
15:38:41
!link https://pagure.io/releng/issues
<@patrikp:matrix.org>
15:39:46
OK, two of them I can do outright, assigned.
<@patrikp:matrix.org>
15:40:37
!releng 12785
<@zodbot:fedora.im>
15:40:39
● **Assignee:** Not Assigned
<@zodbot:fedora.im>
15:40:39
**releng #12785** (https://pagure.io/releng/issue/12785):**out-of-date EPEL repomd.xml references, multiple mirrors, >1 week**
<@zodbot:fedora.im>
15:40:39
<@zodbot:fedora.im>
15:40:39
● **Opened:** a day ago by olagarde
<@zodbot:fedora.im>
15:40:39
● **Last Updated:** 28 minutes ago
<@patrikp:matrix.org>
15:40:48
This one looks like it can be closed.
<@patrikp:matrix.org>
15:43:45
!releng 12779
<@zodbot:fedora.im>
15:43:47
● **Opened:** 4 days ago by julicen
<@zodbot:fedora.im>
15:43:47
**releng #12779** (https://pagure.io/releng/issue/12779):**msedit: Delete commit**
<@zodbot:fedora.im>
15:43:47
● **Assignee:** Not Assigned
<@zodbot:fedora.im>
15:43:47
● **Last Updated:** 4 days ago
<@zodbot:fedora.im>
15:43:47
<@patrikp:matrix.org>
15:45:19
So I'm not sure with this one. The policy is that we don't delete commits?
<@patrikp:matrix.org>
15:50:10
OK, I checked the others and I think they are addressed (waiting for reply from tagged people etc.)
<@nirik:matrix.scrye.com>
15:51:44
no particular tickets from my side
<@patrikp:matrix.org>
15:53:17
Alright, next chair, I can take it.
<@patrikp:matrix.org>
15:53:26
!info Next chair June 30th: Patrik
<@patrikp:matrix.org>
15:53:26
!topic Choose next chair.
<@patrikp:matrix.org>
15:53:36
!topic Discussion / Any other business / Open floor.
<@patrikp:matrix.org>
15:53:47
Anything for the open floor? Or you may have a few minutes back.
<@nirik:matrix.scrye.com>
15:55:04
nothing off hand.
<@patrikp:matrix.org>
15:55:35
!info Thank you all for coming!
<@patrikp:matrix.org>
15:55:35
!endmeeting