15:00:29 #startmeeting RELENG (2021-08-17) 15:00:29 Meeting started Tue Aug 17 15:00:29 2021 UTC. 15:00:29 This meeting is logged and archived in a public location. 15:00:29 The chair is jednorozec. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:29 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:29 The meeting name has been set to 'releng_(2021-08-17)' 15:00:29 #meetingname releng 15:00:29 #chair nirik sharkcz pbrobinson pingou mboddu dustymabe ksinny jednorozec 15:00:29 The meeting name has been set to 'releng' 15:00:29 Current chairs: dustymabe jednorozec ksinny mboddu nirik pbrobinson pingou sharkcz 15:00:43 #topic init process 15:01:23 morning 15:02:37 morning 15:05:25 so we skipped last week, because of the mass branching 15:05:32 * mboddu is kinda here 15:05:32 I have something for open floor 15:06:27 which brings me to the branching. I have read back some messages regarding issues during the branching. Did you write down any of that in one place? nirik mboddu 15:06:57 sadly no, but we can reconstruct it. Where is the sop / doc for it? I couldn't see it off hand 15:07:25 nirik, https://docs.pagure.org/releng/sop_mass_branching.html 15:07:49 Maybe adding an explanation of why we disabled branched signing until a successful rawhide compose would be useful 15:08:14 yes, that would be good. 15:08:20 +1 15:08:57 The ownership of development/35 and fedora-secondary...development/35 wasn't right (needs to be ftpsync) 15:09:06 * nirik tries to recall anything else 15:09:19 jednorozec: https://fedoraproject.org/wiki/Changes/Freeze_after_branching_until_compose_is_ready if you can add it to the SOP 15:09:41 * mboddu cant do it with only one day remaining before PTO 15:09:49 I will 15:10:04 Might add updating koschei 15:10:19 mboddu, just throw relevant stuff my way I will put it together/update 15:10:43 I think there was something with bodhi, but now I would have to go look at logs, can't recall what it was 15:10:44 nirik, is that documented some where? 15:10:55 nirik: Also the distgit repos sync thing 15:11:04 nirik, yes tags in bodhi 15:11:11 yeah, there is a infra-doc/koschei doc on how to do it, but it just needs doing. Basically oc rsh into an admin pod and run a command 15:11:12 the releases had wrong tags 15:11:21 grokmirror 15:11:32 and what is that? mboddu 15:11:33 oh yeah, I still haven't done that oen. 15:11:42 * nirik sighs. so much to do. so so much. 15:12:28 I have seen the issue about grokmirror but dont know what it is and where 15:12:32 jednorozec: Its a dist-git git repos mirroing thing - https://fedoraproject.org/wiki/Infrastructure/Grokmirror 15:12:57 I also dont know how to fix it, nirik only knows about it 15:13:00 so another thing to add to the SOP 15:13:35 in theory it should fix itself... but I guess it didn't. there's a releng ticket on it right? 15:13:46 yes there is 15:14:14 SO I will take the log from this meeting and update branching sop 15:14:26 nirik: Nope, its an infra ticket 15:14:34 they all blur. ;) 15:14:53 well this one? 15:14:53 https://pagure.io/releng/issue/10270 15:15:01 .releng 10270 15:15:01 jednorozec: Also, not related to branching but can you help with https://src.fedoraproject.org/rpms/fedora-repos/pull-request/112#comment-83490 15:15:01 jednorozec: Issue #10270: Refresh Grokmirror manifest - releng - Pagure.io - https://pagure.io/releng/issue/10270 15:15:47 mboddu, ack 15:17:33 So i was fixing issue during the mass branch 15:18:05 our scripts import fedscm_admin to get some data. And it includes fasjson and it failed horibly on infra machines 15:19:35 this should be all regarding mass branching. 15:19:48 I will take the minutes and include/update info in the SOP 15:25:52 sounds good 15:25:57 .releng 10270 15:25:58 jednorozec: Issue #10270: Refresh Grokmirror manifest - releng - Pagure.io - https://pagure.io/releng/issue/10270 15:26:07 so how do one fix this? 15:27:19 I would have to look at it again. I don't recall off the top of my head. There's a command to regenerate the manifest, but it's buggy and memory intensive... 15:28:12 nirik, if you can point me to where is it running I can look around. 15:28:40 it's on pkgs01. 15:28:56 ok I will read the docs and look into it 15:29:00 it's supposed to pick up new repos when it runs. 15:29:40 that would be great. :) feel free to ask me about it or schedule time to look at it and I can look more in depth... 15:32:38 If I am unable to find a solution, will schedule something tomorrow. 15:32:53 .releng 10251 15:32:55 jednorozec: Issue #10251: Unretire python3-nss package - releng - Pagure.io - https://pagure.io/releng/issue/10251 15:33:25 so, I would close and ask them to re-open if they really want to do it? 15:33:49 ack 15:34:02 which I think would be a bad idea, but hey... 15:35:49 .releng 10264 15:35:50 jednorozec: Issue #10264: New Repo for "rpms/pypy3.7" incompletely created - releng - Pagure.io - https://pagure.io/releng/issue/10264 15:36:18 this is fedscm_admin issue as miro pointedout --no-initial-commit is causing this 15:37:31 ah ha 15:38:37 so easiest and dirties fix is to ignore --no-initial-commit parameter 15:39:31 but I am not sure how to properly fix this 15:41:45 dunno... 15:43:54 there may be some git magic that can do branches and aliases without commits 15:44:00 needs more investigation 15:44:17 lets move on 15:44:20 .releng 10073 15:44:21 jednorozec: Issue #10073: Fedora-34-Beta .composeinfo file - releng - Pagure.io - https://pagure.io/releng/issue/10073 15:44:42 so are we going to do that with f35? 15:45:35 that would be nice. 15:45:38 is that a pungi change? 15:45:48 I think so 15:45:50 let me check 15:48:31 so there is nothing like fedora-version in the pungi config 15:48:51 it might construct it? 15:49:09 so it is most probably somehow composed of fedora and %version% variable 15:49:16 nirik, yup 15:49:27 so needs some investigation I guess 15:49:52 exactly 15:50:25 but I would like to have it in f35 if possible 15:51:18 so 15:51:27 we have less than 10minutes 15:51:50 #topic Open Floor 15:51:59 mboddu, you have something? 15:53:09 jednorozec: Yes, I will going on PTO starting tomorrow til the end of next week 15:53:21 We have beta freeze and bodhi enablement next week 15:54:13 I *might* be around but not guaranteed 15:54:21 The SOP's are up to date afaik 15:54:31 Ping me if you need any help 15:54:38 I think we did it together last 2 times 15:54:46 Yup 15:54:48 That is all 15:55:01 * jednorozec will go through the SOP and check all the steps tomorrow 15:55:18 so if there is any confusion on my side we can solve it befor your PTO 15:55:33 oh 15:55:37 I will be off tomorrow, but ping me, I will see what I can do 15:55:49 mboddu, ahh it starts tomorrow 15:55:56 Yup 15:56:11 I'm happy to help with anything related to it too 15:56:11 enjoy your time off! 15:56:36 Thanks jednorozec 15:56:56 I have one more thing for open floor 15:57:13 I have identified some compose failures. dues to retired packages. 15:57:30 sould I just remove them from kickstarts? 15:57:52 I'd say so yeah. 15:59:47 will do that 16:00:09 #endmeeting