<@humaton:fedora.im>
17:00:17
!startmeeting RELENG (2023-11-28)
<@meetbot:fedora.im>
17:00:18
Meeting started at 2023-11-28 17:00:17 UTC
<@meetbot:fedora.im>
17:00:18
The Meeting name is 'RELENG (2023-11-28)'
<@humaton:fedora.im>
17:00:23
!meetingname releng
<@humaton:fedora.im>
17:00:29
!chair nirik sharkcz pbrobinson phsmoura dustymabe jednorozec
<@humaton:fedora.im>
17:00:35
!topic init process
<@nirik:matrix.scrye.com>
17:00:47
!hi
<@zodbot:fedora.im>
17:00:48
Kevin Fenzi (kevin) - he / him / his
<@humaton:fedora.im>
17:01:04
!hi
<@zodbot:fedora.im>
17:01:05
Tomáš Hrčka (humaton) - he / him / his
<@humaton:fedora.im>
17:01:14
heh :)
<@patrikp:matrix.org>
17:02:01
!hi
<@zodbot:fedora.im>
17:02:03
No Fedora Accounts users have the @patrikp:matrix.org Matrix Account defined
<@nirik:matrix.scrye.com>
17:04:31
whats our agenda today?
<@humaton:fedora.im>
17:04:50
I have few updates and some questions
<@nirik:matrix.scrye.com>
17:04:56
I wanted to talk about builders/f39
<@humaton:fedora.im>
17:05:13
there was my questions
<@humaton:fedora.im>
17:05:19
did I break things in stg?
<@humaton:fedora.im>
17:05:31
and the createrepo_c thing
<@nirik:matrix.scrye.com>
17:05:41
yeah... but totally not your fault...
<@nirik:matrix.scrye.com>
17:06:54
we are running a koji package version that has a few patches on it... needed a new f39 build of that. Without it, kojid was failing to run on builders because a missing plugin we asked it to load. :)
<@humaton:fedora.im>
17:07:23
hmmm
<@nirik:matrix.scrye.com>
17:07:24
so, we should add to the SOP to check koji version and make sure any local builds are done/ready first
<@nirik:matrix.scrye.com>
17:08:25
https://koji.fedoraproject.org/koji/buildinfo?buildID=2325277 is the f39 one... staging should be updated to that and happy now.
<@nirik:matrix.scrye.com>
17:10:31
which brings us to the other thing... we can't do prod yet.
<@humaton:fedora.im>
17:10:36
and those patches are living somewhere?
<@nirik:matrix.scrye.com>
17:11:19
in the src.rpm in koji... but I think all of them are upstream now, just not in a release...
<@nirik:matrix.scrye.com>
17:12:19
one is a theme tweak, one is a debugging add and the last is the scmpolicy plugin, which they were going to land upstream.
<@humaton:fedora.im>
17:13:01
ok, so rebuild from srpm into -infra tag
<@nirik:matrix.scrye.com>
17:13:31
yep. I don't see the scmpolicy plugin yet upstream, will poke them about that.
<@humaton:fedora.im>
17:14:23
I will send PR for the SOP
<@nirik:matrix.scrye.com>
17:14:28
+1
<@nirik:matrix.scrye.com>
17:15:53
So, on prod... new f39 createrepo_c will make repos that epel7/rhel7 can't understand... so, we need to wait until: rhel7 goes eol, or more likely until createrepo_c + koji can work something to handle this case. Probibly a way to set on a tag that it needs older createrepo_c repodata and a way to pass that into createrepo_c...
<@nirik:matrix.scrye.com>
17:16:36
so thats just on hold until then I guess. :(
<@humaton:fedora.im>
17:16:42
Yeah I thought so after the ticket was opened for that
<@humaton:fedora.im>
17:18:24
Hmm
<@humaton:fedora.im>
17:18:33
el7 EOL is in Jun 24
<@humaton:fedora.im>
17:18:49
so we will build f40 on f38 builders?
<@humaton:fedora.im>
17:19:24
but hopefully things get sorted out in koji by then
<@nirik:matrix.scrye.com>
17:19:46
yeah, I really hope for sooner.
<@nirik:matrix.scrye.com>
17:20:52
I suppose we could...
<@nirik:matrix.scrye.com>
17:21:18
upgrade all the machines except some few and force all the createrepos there, but there's... a vast sea of them, so that would slow things a lot.
<@humaton:fedora.im>
17:22:04
maybe as extra last resort if nothings gets done on koji/createrepo_c side of things?
<@humaton:fedora.im>
17:22:33
and we need the upgrade because change X requires what ever...
<@nirik:matrix.scrye.com>
17:23:05
yeah, I'd prefer not to do that... but it's an option if we need it.
<@nirik:matrix.scrye.com>
17:24:04
sadly we can't just direct epel7 newrepos to some... it's all or nothing I think.
<@humaton:fedora.im>
17:25:15
I wanted to ask you about this.
<@humaton:fedora.im>
17:25:19
.releng 11801
<@humaton:fedora.im>
17:25:36
!releng 11801
<@zodbot:fedora.im>
17:25:36
releng #11801 (https://pagure.io/releng/issue/11801): Please retarget f39-toolchain to rawhide/f40
<@humaton:fedora.im>
17:25:41
so
<@humaton:fedora.im>
17:26:08
is there a big difference between rename/retarget things and creating new tag/target ?
<@humaton:fedora.im>
17:27:23
what I want to ask is if the outcome is the same. Because I find it simpler to just recreate those that to fiddle with editing
<@nirik:matrix.scrye.com>
17:28:42
yeah, should be the same... so, I'd say, remove the f39 target, make new f40 one and... add to our branching docs to just do it at branching time? (if thats ok with requestor?)
<@nirik:matrix.scrye.com>
17:29:15
I mean even if it's called 'rawhide-toolchain' we will have to change it at branching to point to the new rawhide...
<@humaton:fedora.im>
17:29:30
right
<@humaton:fedora.im>
17:29:38
but they target f40
<@humaton:fedora.im>
17:30:05
but yeah I will add it to the branching tasks and check with them
<@nirik:matrix.scrye.com>
17:30:18
right now, yes... but when f40 branches... I bet they want to target f41
<@humaton:fedora.im>
17:30:26
:D
<@humaton:fedora.im>
17:30:30
right
<@humaton:fedora.im>
17:30:43
multilib question
<@humaton:fedora.im>
17:30:55
!releng 11800
<@zodbot:fedora.im>
17:30:56
releng #11800 (https://pagure.io/releng/issue/11800): Please add both obs-studio-libs and obs-studio-plugin-vkcapture to the multilib whitelist
<@humaton:fedora.im>
17:31:37
so should we add it? samyak already created PR fro pungi-fedora
<@humaton:fedora.im>
17:32:01
I just didnt merge it because I dont like 32bit stuff
<@humaton:fedora.im>
17:32:15
wanted to have another ack before doing that.
<@nirik:matrix.scrye.com>
17:32:26
yeah, I suppose... note that we also have to add it in infra-ansible... for bodhi.
<@humaton:fedora.im>
17:32:39
Aaaaa!
<@humaton:fedora.im>
17:32:51
let me comment on the PR so we dont forget
<@nirik:matrix.scrye.com>
17:32:52
I also don't like em, but sure... we haven't completely killed it yet.
<@nirik:matrix.scrye.com>
17:33:43
:thumbs_up
<@nirik:matrix.scrye.com>
17:33:46
oops.
<@nirik:matrix.scrye.com>
17:33:53
👍
<@humaton:fedora.im>
17:35:22
its the gamers they are still running 32b stuff
<@nirik:matrix.scrye.com>
17:35:35
yep. :(
<@humaton:fedora.im>
17:36:18
which is sad because in some ways gaming did a lot of innovation, just not moving forward in this direction
<@nirik:matrix.scrye.com>
17:36:41
Someday you have to let the old closed source game go... ;)
<@nirik:matrix.scrye.com>
17:36:54
anyhow, I wanted to mention schedule stuff too...
<@nirik:matrix.scrye.com>
17:37:29
We have a few things coming up (including today!)
<@nirik:matrix.scrye.com>
17:37:53
REMINDER: EOL release final update push in 1 week Tue 2023-11-28 Tue 2023-11-28 0 REMINDER: EOL release final update push in 1 day Mon 2023-12-04 Mon 2023-12-04 0
<@nirik:matrix.scrye.com>
17:38:19
then f37 EOL on 12-05 I think?
<@humaton:fedora.im>
17:38:21
yup
<@humaton:fedora.im>
17:39:27
I see no templete for the reminder
<@nirik:matrix.scrye.com>
17:39:31
can you send the reminders? I can if no one else...
<@humaton:fedora.im>
17:39:38
I can np
<@nirik:matrix.scrye.com>
17:39:40
oh? missed it I guess.
<@humaton:fedora.im>
17:39:47
let me just search inbox for previous
<@nirik:matrix.scrye.com>
17:39:58
yeah, there should be old ones to make a new template from.
<@humaton:fedora.im>
17:41:32
oh so I used the EOL template just $subj was 1 week
<@nirik:matrix.scrye.com>
17:42:42
seems like it might be slightly different...
<@nirik:matrix.scrye.com>
17:42:46
or should be
<@nirik:matrix.scrye.com>
17:45:50
I have some issues to propose closing... :)
<@nirik:matrix.scrye.com>
17:46:00
!releng 11480
<@zodbot:fedora.im>
17:46:05
releng #11480 (https://pagure.io/releng/issue/11480): Changes/RetireModularity
<@nirik:matrix.scrye.com>
17:46:13
this should be all done I think?
<@humaton:fedora.im>
17:46:34
I think so
<@nirik:matrix.scrye.com>
17:47:52
!releng 11761
<@zodbot:fedora.im>
17:47:53
releng #11761 (https://pagure.io/releng/issue/11761): missing artifacts from f39-rc-1.5 (final release)
<@nirik:matrix.scrye.com>
17:47:59
this should be all done right?
<@nirik:matrix.scrye.com>
17:48:09
or we still need torrents?
<@humaton:fedora.im>
17:49:11
can you just checks before I hit send? https://paste.centos.org/view/9fc14720
<@humaton:fedora.im>
17:49:59
oh the torrents we have them but not in place, I think I have copy of them in my home
<@nirik:matrix.scrye.com>
17:50:38
Might put 'stable ' before bodhi? to let them know they must be requested/pushed stable before then...
<@nirik:matrix.scrye.com>
17:51:06
also, might add a link to the template for improvement suggestions (like we have on others?)
<@nirik:matrix.scrye.com>
17:51:20
ah, ok, then we can leave that ticket open until those are there.
<@humaton:fedora.im>
17:52:35
ahh ket me rephrase that
<@nirik:matrix.scrye.com>
17:52:47
I see some unretires seem stalled... 11793 , 11740 , 11721 , 11692
<@nirik:matrix.scrye.com>
17:53:46
I guess some are because they needed re-review. Should we close them and tell them to open a new one after review is + ?
<@humaton:fedora.im>
17:55:36
So
<@humaton:fedora.im>
17:55:39
yeah we can do that
<@humaton:fedora.im>
17:55:53
but what people tend to do is to open a new ticket instead
<@humaton:fedora.im>
17:56:01
there is template response for it
<@humaton:fedora.im>
17:56:06
but it happened once :D
<@humaton:fedora.im>
17:56:24
I think all of them are waiting for review
<@nirik:matrix.scrye.com>
17:56:27
yeah. In fact I think at least one of those already did that and the old ticket is still open...
<@humaton:fedora.im>
17:56:31
some are in progress some stalled
<@nirik:matrix.scrye.com>
17:57:02
at least orage is already built and available .
<@nirik:matrix.scrye.com>
17:57:23
which makes me think even more we should close those. ;) Or else they just sit there forever.
<@humaton:fedora.im>
17:57:51
So i put link for stable updates to the email aswell https://paste.centos.org/view/2e73a360
<@humaton:fedora.im>
17:58:07
hmm
<@humaton:fedora.im>
17:58:13
did I forget to close some?
<@humaton:fedora.im>
17:58:18
might be the case
<@nirik:matrix.scrye.com>
17:58:44
LGTM. +1
<@humaton:fedora.im>
17:58:48
So i wanted to talk about this one
<@humaton:fedora.im>
17:58:53
!releng 11802
<@zodbot:fedora.im>
17:58:54
releng #11802 (https://pagure.io/releng/issue/11802): New repository request for qatengine
<@nirik:matrix.scrye.com>
17:59:31
IMHO -> close cantfix.
<@humaton:fedora.im>
17:59:38
it is clear violation of fedora packaging guides as pointed by carl
<@humaton:fedora.im>
17:59:57
Yeah
<@nirik:matrix.scrye.com>
18:00:19
they could make a epel package... but it should pass through review and the normal process.
<@nirik:matrix.scrye.com>
18:01:03
we should also direct them to the epel matrix channel to discuss more...
<@humaton:fedora.im>
18:01:17
right I was going to point them to the package review process but carl was faster with response that makes since he is also epel guy
<@humaton:fedora.im>
18:03:46
oh
<@humaton:fedora.im>
18:03:49
we are over time
<@nirik:matrix.scrye.com>
18:04:06
yep. ;)
<@humaton:fedora.im>
18:04:10
no time for PDC updates, but work is moving we are de-PDCfing stuff
<@nirik:matrix.scrye.com>
18:04:17
hurray!
<@humaton:fedora.im>
18:04:45
will need to do pagure release preferably before holidays
<@humaton:fedora.im>
18:04:51
thanks for your time
<@humaton:fedora.im>
18:04:54
!endmeeting