16:00:34 <jednorozec> #startmeeting RELENG (2023-05-23)
16:00:34 <zodbot> Meeting started Tue May 30 16:00:34 2023 UTC.
16:00:34 <zodbot> This meeting is logged and archived in a public location.
16:00:34 <zodbot> The chair is jednorozec. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:00:34 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:00:34 <zodbot> The meeting name has been set to 'releng_(2023-05-23)'
16:00:34 <jednorozec> #meetingname releng
16:00:35 <zodbot> The meeting name has been set to 'releng'
16:00:35 <jednorozec> #chair nirik sharkcz pbrobinson phsmoura dustymabe jednorozec
16:00:35 <jednorozec> #topic init process
16:00:35 <zodbot> Current chairs: dustymabe jednorozec nirik pbrobinson phsmoura sharkcz
16:00:49 <nirik> morning
16:01:33 <jednorozec> hello
16:02:12 <jednorozec> I will not manage whole hour of the meeting
16:02:29 <jednorozec> had some train food on the road and it was not a good idea...
16:02:49 <nirik> I'm pretty groggy myself. (Had to pick someone up at the airport last night and didn't get home until 1am)
16:03:00 <nirik> oof. Not fun
16:03:37 <jednorozec> so
16:03:58 <jednorozec> I dont get to do much in the start of week every 14 days
16:04:00 <jednorozec> like now
16:04:19 <jednorozec> but I have noticed that there is no clear documentation on how too retire modules
16:04:24 <jednorozec> .ticket 11351
16:04:27 <zodbot> jednorozec: Issue #11351: Retire cri-o module and go back to publishing cri-o and cri-tools as RPMs - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/11351
16:04:47 <jednorozec> .releng 11405
16:04:48 <zodbot> jednorozec: Issue #11405: retire ghc module streams - releng - Pagure.io - https://pagure.io/releng/issue/11405
16:05:26 <jednorozec> I checked the modularity docs and infra&releng docs
16:05:31 <jednorozec> and there is nothing
16:05:53 <jednorozec> or I might be blind if there is anything please throw it this way
16:05:56 <nirik> yeah, I think you have to update some kind of module thing, but I can't recall the details.
16:06:07 <jednorozec> module-defaults?
16:06:12 <nirik> yeah
16:06:17 <jednorozec> that is a repo I found with almoas none info about it :D
16:06:20 <nirik> but yeah, docs/sop would be very good.
16:07:36 <nirik> yeah. ;(
16:07:51 <jednorozec> well documentation is never ending story
16:08:06 <jednorozec> puting it on todo list.
16:08:31 <jednorozec> looking at the tracker, I actually didnt sync compose data for openh264
16:08:45 <jednorozec> .releng 11422
16:08:46 <zodbot> jednorozec: Issue #11422: Please send openh264-2.3.1-1.el9 to Cisco - releng - Pagure.io - https://pagure.io/releng/issue/11422
16:08:51 <nirik> did cisco finish uploading?
16:08:54 <jednorozec> let me do that now before I forget again
16:08:56 <jednorozec> yes
16:09:02 <jednorozec> last week  :(
16:09:06 <jednorozec> my bad
16:09:33 <nirik> ok. yeah...
16:09:45 <nirik> I had just a few hopefully quick items.
16:10:56 <jednorozec> go for it I am running the rsync and will put things in place
16:11:49 <nirik> First, there's still discussion on the devel list about the toolbx container... I guess we will wait and see a bit longer? it might be that we can just make it with imagefactory/kickstart and that would be much easier for us. ;)
16:12:33 <nirik> Second, there's a s390x outage thursday, so I decided to just do a koji database upgrade at the same time since things would be down anyhow. ;)
16:13:06 <nirik> Want to move bvmhost-x86-01 and db-koji to rhel9. newer postgresql (16 vs 12) should perhaps help performance.
16:13:43 <jednorozec> Yeah I have seen the discussion, but my feeling is they do not want to do that
16:14:08 <nirik> They are reluctant, but otaylor is trying to convince. ;)
16:14:22 <jednorozec> :)
16:17:14 <nirik> oh, also on thursday I was going to update koji to 1.33.0 and the new theme
16:17:25 <jednorozec> weeee
16:17:28 <nirik> (see stg koji for new theme, ryan made it)
16:17:46 <jednorozec> it looks nicer
16:18:04 <jednorozec> hmm we never shipped openh264 for any epel release
16:18:23 <jednorozec> there are just 24-38 numbers on sundries
16:18:30 <nirik> yeah, this is the first
16:18:35 <jednorozec> should it be el9 or epel9 ?
16:18:37 <nirik> I think the others didn't have all the deps.
16:18:47 <nirik> epel9 I would think
16:21:24 <nirik> I'm not sure I have anything else...
16:23:31 <jednorozec> things are in place on sundries and mm
16:23:53 <nirik> cool. I don't know if we will have to do more in mm for it to see it or not. ;)
16:24:04 <nirik> we will likely have to add it to epel-release/repos
16:24:15 <jednorozec> ah
16:25:11 <nirik> but we can do those things as we find em.
16:25:46 <jednorozec> ok I have to run
16:25:56 <jednorozec> literally...
16:26:01 <jednorozec> #endmeeting