15:01:40 <jednorozec> #startmeeting RELENG (2022-06-14)
15:01:40 <zodbot> Meeting started Tue Jun 14 15:01:40 2022 UTC.
15:01:40 <zodbot> This meeting is logged and archived in a public location.
15:01:40 <zodbot> The chair is jednorozec. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
15:01:40 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:01:40 <zodbot> The meeting name has been set to 'releng_(2022-06-14)'
15:01:40 <jednorozec> #meetingname releng
15:01:40 <zodbot> The meeting name has been set to 'releng'
15:01:40 <jednorozec> #chair nirik sharkcz pbrobinson phsmoura dustymabe jednorozec
15:01:40 <jednorozec> #topic init process
15:01:40 <zodbot> Current chairs: dustymabe jednorozec nirik pbrobinson phsmoura sharkcz
15:01:42 <jednorozec> sorry
15:01:51 <bittin> np
15:01:53 <phsmoura> morning
15:01:54 <nirik> no worries. morning
15:01:57 <bittin> afternoon
15:02:53 <jednorozec> so what do we have here for today?
15:03:24 <nirik> I didn't have anything urgent. we could go thru tickets or discuss whatever folks would like
15:03:49 <bittin> same don't have anything urgent just had some extra time
15:04:29 <jednorozec> same here, just a note about ODCS being broken
15:04:58 <jednorozec> we need to document our deployments little bit more, ansible playbook is not necessarly a documentation :)
15:05:21 <nirik> yeah, sorry about that... but the f32 backend needed replacing. I didn't realize that the versions wouldn't be compatible
15:05:52 <jednorozec> well that just had to be done
15:05:56 <jednorozec> no questions about that
15:06:18 <jednorozec> also it breaks so it breaks, that is normal.
15:06:24 <nirik> I'm not sure why it was fedora in the first place rather than rhel8...
15:06:37 <nirik> but I figured there was some reason, so I kept it fedora
15:06:45 <jednorozec> But there is not much to find about the service deployment it self like
15:07:10 <jednorozec> why it has multiple backends and what funcion they have
15:07:11 <jednorozec> and so
15:07:39 <nirik> The -releng backend was setup with more resources at some time when it was unclear who was going to be using it for what.
15:07:52 <nirik> but yeah, it would be more clear if it just had one backend...
15:08:08 <jednorozec> or 2 or 3 but with a few lines why
15:08:15 <nirik> my understanding is that it's used by:
15:08:30 <nirik> eln composes, fedora minimal composes? and flatpaks
15:08:52 <nirik> (we are talking about odcs... on demand compose service)
15:09:47 <jednorozec> I am not sure about the flatpaks, but now I know how to findout and document it :)
15:10:07 <nirik> I suppose we have a SOP for it? lets see
15:10:13 <jednorozec> yup
15:10:17 <jednorozec> but not much info there
15:10:51 <jednorozec> https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/odcs/
15:11:10 <nirik> yeah. also very out of date. ;)
15:11:28 <jednorozec> I am adding deployment section with info about how it is done
15:11:44 <jednorozec> and package version mismatch into the what could go wrong section
15:12:39 <nirik> yeah, and the releng-backend01 and what it's used for.
15:12:48 <nirik> also, there's no factory2 team anymore
15:13:06 <jednorozec> yup that would be covered in the deployment section
15:13:34 <jednorozec> anyway that is all I had for this topic
15:13:41 <nirik> and releng01 has a cron for eln composes
15:14:52 <jednorozec> so lets look at the tickets
15:15:02 <jednorozec> I think we can move with this one
15:15:03 <jednorozec> .releng 10794
15:15:04 <zodbot> jednorozec: Issue #10794: Enable rpm signing for F-37 - releng - Pagure.io - https://pagure.io/releng/issue/10794
15:15:19 <jednorozec> now we have info about the key that is needed
15:15:48 <nirik> ah yeah. +1
15:16:00 <bittin> +1
15:16:57 <nirik> where was that docs pr again?
15:17:11 <jednorozec> https://pagure.io/releng/pull-request/10825#request_diff
15:18:04 <nirik> ok, I was looking on docs.pagure.org. ;)
15:18:12 <jednorozec> huh
15:18:15 <jednorozec> its is not there
15:18:18 <jednorozec> hmm
15:18:22 <jednorozec> Let me update it
15:18:23 <nirik> yeah, thats manually updated.
15:18:32 <bittin> docs.pagure.org is 404
15:18:35 <nirik> you have to build it and check it in or something.
15:18:47 <nirik> https://docs.pagure.org/releng/
15:18:54 <bittin> ah
15:19:20 <nirik> we really should convert these over to docs.fedoraproject.org with/next to the infra ones.
15:20:03 <jednorozec> we should, but the docs.fedoraproject.org is soo ugly
15:20:05 <nirik> anyhow, we need to make a fedora-37-ima and a fedora-38-ima keys (since we want to stay 1 ahead). I can do that, or you can jednorozec
15:20:43 <jednorozec> nirik, I probably cannot
15:21:18 <jednorozec> or can I?
15:21:21 <nirik> oh? I would think you could...
15:22:42 <nirik> just make sure to add me for access and admin... to avoid the lottery factory
15:22:45 <nirik> factor
15:24:05 <jednorozec> ok, I will try to create them
15:24:22 <nirik> cool. :)
15:25:46 <jednorozec> pushing the new docs meanwhile
15:29:05 <bittin> any more tickets?
15:30:11 <jednorozec> .releng 10798
15:30:12 <zodbot> jednorozec: Issue #10798: impact of https://fedoraproject.org/wiki/Changes/JdkInTreeLibsAndStdclibStatic to rcm - releng - Pagure.io - https://pagure.io/releng/issue/10798
15:30:25 <jednorozec> did any of you followed the discussions on devel thread?
15:30:31 <jednorozec> will this be real?
15:30:39 <jednorozec> I stopped afte rfew days
15:30:44 * bittin did not
15:31:09 * nirik did
15:31:35 <nirik> this part was approved...
15:31:46 <nirik> but if doesn't affect releng any that I can think of.
15:31:53 <jednorozec> yeah
15:31:57 <jednorozec> so we can close it
15:31:59 <jednorozec> :)
15:32:16 <nirik> the other parts of this seem unlikely to pass fesco...
15:32:38 <nirik> one part of which has a lot of impact on releng. The 'build once and tag into other releases' thing.
15:32:55 <jednorozec> yeah
15:33:03 <jednorozec> there was a heated discussion about that
15:33:07 <jednorozec> on devel list
15:33:41 <jednorozec> also noreleng change.
15:33:44 <jednorozec> .releng 10836
15:33:45 <zodbot> jednorozec: Issue #10836: F37 Change: Gettext Runtime Subpackage - releng - Pagure.io - https://pagure.io/releng/issue/10836
15:35:08 <nirik> yeah, no releng changes here I can see either
15:35:16 <bittin> sounds good
15:35:31 <jednorozec> another one
15:35:35 <jednorozec> .releng 10720
15:35:36 <zodbot> jednorozec: Issue #10720: F37: Self contained change: Support FIDO Device Onboarding - releng - Pagure.io - https://pagure.io/releng/issue/10720
15:36:12 <nirik> yeah, same here, no releng impact I don't think.
15:37:44 <jednorozec> yeah i tried to tag them no-releng when I was sure they have 0 impact on us
15:37:51 <jednorozec> but want to have it checked
15:38:37 <jednorozec> another java one
15:38:39 <jednorozec> .releng 10686
15:38:40 <zodbot> jednorozec: Issue #10686: Drop i686 builds of jdk8,11,17 and latest (18) rpms from f37 onwards - releng - Pagure.io - https://pagure.io/releng/issue/10686
15:39:59 <nirik> well, I would say no releng impact, but not sure about their question...
15:41:04 <jednorozec> they dont want to include excludearch in java packages
15:41:29 <jednorozec> and want us to stop building x86 java packages
15:42:18 <nirik> yeah, but I don't get the noarch part.
15:42:32 <nirik> they don't want to build a noarch subpackage on i686.
15:42:39 <jednorozec> right
15:42:41 <nirik> but... if it's noarch, it shouldn't matter?
15:43:00 <jednorozec> well
15:43:22 <nirik> also, koji builds noarch packages for every arch... and checks to make sure they are the same...
15:43:30 <jednorozec> yeah
15:44:30 <nirik> so, I guess we should ask them to clarify...
15:44:56 <nirik> https://kojipkgs.fedoraproject.org//packages/java-1.8.0-openjdk/1.8.0.332.b09/1.fc36/data/logs/i686/noarch_rpmdiff.json
15:44:58 <nirik> for example
15:45:43 <nirik> or perhaps they mean _other_ java packages?
15:46:57 <jednorozec> I think they mean alll java packages but jdk
15:46:59 <nirik> yeah, re-reading that seems like it. They exclude i686 from the openjdk, but want to know how to make all noarch java packages not try and build on i686 where there's no openjdk
15:47:18 <jednorozec> that is what i read
15:47:29 <nirik> I'm afraid we don't have any way to do that off hand.
15:50:10 <jednorozec> ok moving on
15:50:13 <jednorozec> this one on the top
15:50:16 <jednorozec> .releng 10832
15:50:17 <zodbot> jednorozec: Issue #10832: I can't push FEDORA-2022-0feca8b2c9 to stable - releng - Pagure.io - https://pagure.io/releng/issue/10832
15:50:36 <jednorozec> I tried to disable all checks for that update, but nothing
15:50:39 <nirik> yeah, I poked at it, but failed to get it to do anything. ;( I was hoping that mattia could look
15:50:57 <nirik> did you want to update 10686? or want me to?
15:51:17 <bittin> jednorozec did it
15:51:50 <x3mboy> .nextmeetings
15:51:51 <zodbot> x3mboy: One moment, please...  Looking up the channel list.
15:51:54 <zodbot> x3mboy: b'In #fedora-i3 is Fedora i3wm SIG (starting in 8 minutes)'
15:51:57 <zodbot> x3mboy: b'In #fedora-meeting is FESCo Meeting (starting in an hour)'
15:52:00 <zodbot> x3mboy: b'In #fedora-admin is Fedora Infra Ops Daily Standup (starting in 2 hours)'
15:52:03 <zodbot> x3mboy: b'In #fedora-meeting-1 is FPgM office hours (starting in 21 hours)'
15:52:06 <zodbot> x3mboy: b'In #fedora-meeting-1 is Prioritized bugs and issues (starting in a day)'
15:52:13 <jednorozec> x3mboy, that is little rude to interupt our meeting
15:52:28 <x3mboy> Oh sorry, I didn't notice you were at meeting
15:52:33 <x3mboy> I'm so so sorry
15:52:39 <nirik> no biggie
15:52:39 <x3mboy> My very sincere apologize
15:52:46 <jednorozec> its ok :)
15:53:03 <jednorozec> this chanell is probably used only for 2 meetings
15:53:38 <jednorozec> anyway the update
15:54:02 <jednorozec> it seems to me that it got cought in some random state because it had -1 karma before the update
15:54:12 <jednorozec> and we updated bodhi to v 6.0
15:54:17 <jednorozec> and this hapenned
15:54:44 <nirik> might be.
15:55:07 <nirik> I think it might be because someone pushed it stable... and in rawhide you normally have bodhi decide when things should go stable
15:56:30 <jednorozec> hm
15:57:04 <nirik> but not sure. I looked at logs...
15:57:20 <nirik> and it shows the edits, but nothing else. it just ignores it when it's processing otherwise.
16:00:24 <jednorozec> they are asking if rebuild in different side-tag would help
16:00:45 <jednorozec> it probably wont because there is already update for that NVR
16:01:13 <nirik> yeah it would work if they bumped release again.
16:02:36 <jednorozec> wrote a comment there
16:02:45 <jednorozec> and we are at the end
16:02:51 <nirik> oh yeah, out of time. ;)
16:02:58 <jednorozec> #endmeeting