15:00:11 #startmeeting RELENG (2022-05-17) 15:00:11 Meeting started Tue May 17 15:00:11 2022 UTC. 15:00:11 This meeting is logged and archived in a public location. 15:00:11 The chair is jednorozec. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 15:00:11 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:11 The meeting name has been set to 'releng_(2022-05-17)' 15:00:11 #meetingname releng 15:00:11 The meeting name has been set to 'releng' 15:00:11 #chair nirik sharkcz pbrobinson phsmoura dustymabe jednorozec 15:00:11 #topic init process 15:00:11 Current chairs: dustymabe jednorozec nirik pbrobinson phsmoura sharkcz 15:01:01 morning/ 15:01:14 sort of here, sort of trying to get a machine working again 15:01:18 morning 15:01:36 I just got online, there was a planned outage in our village 15:01:43 and it lasted full 8hrs 15:02:18 * jednorozec turning on all the computers 15:02:42 power outage? 15:02:56 yes, planned one for maintanance or what ever 15:03:19 they usually finish within 2-4hrs but this year it took half of the day 15:04:57 I forgot about it and all my machines where running when they disconnected the power 15:05:57 but znc & storage seems to be working, everything else at least blinks 15:06:09 so 15:06:21 since I have not seen our tracker let me have a look 15:07:10 .releng 10797 15:07:19 let me check what is wrong there 15:08:20 jednorozec: Issue #10797: request-branch for epel9 branch by epel-packagers-sig member is rejected - releng - Pagure.io - https://pagure.io/releng/issue/10797 15:12:33 ok so this is a bug in fedscm_Admin 15:12:55 it seems to ignore groups memebership for packages in distgit 15:13:40 huh, you would think it would have been complained about before now... 15:13:51 well 15:14:08 most of the people usually requests themselfs + epelpackagers 15:14:19 so it might not 15:17:13 ok moved to upstream tracker 15:17:27 I will look into it there 15:18:40 thanks 15:19:35 this one was opened in ifra tracker 15:19:42 .infra 10686 15:19:48 .ticket 10686 15:19:50 jednorozec: Issue #10686: F36 images from GCP are not available for download from cloud images page. - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10686 15:19:58 ah yeah, was gonna ask you about that one 15:20:09 so the file + checksum is in place 15:20:23 in unsupported/36/Cloud 15:20:43 but I am struggling to find a repo for getfedora so I can open PR or ticket there 15:21:29 of unofficial not unsupported sorry 15:21:30 https://download-ib01.fedoraproject.org/pub/alt/unofficial/releases/36/x86_64/images/ 15:21:56 yeah, let me see... 15:22:24 https://pagure.io/fedora-web/websites/ I think 15:22:35 davdunc, we are jsut talkign about the GCP image 15:22:59 jednorozec: perfect timing! 15:23:00 nirik, thanks! 15:23:09 I think thats the right place 15:23:55 it seems it is 15:24:06 so I will open PR with correc links to the GCP image 15:24:29 jednorozec: is there something I can help maintain here that will be beneficial in coming releases 15:25:01 I can add the process to our release checklist if it is recurring. 15:25:29 not really it is build automaticaly, but there was random issue during the compose that was marked as GOLD 15:25:44 this is not something we usually have to do... 15:26:31 got it. Thanks for looking into it. 15:26:35 davdunc[m: how is that image usually consumed? 15:26:59 ie, do people go to getfedora.org and get it? or do we/someone upload it to GCP and they can select it from there? 15:27:13 both nirik 15:27:23 ah, fair enough. 15:27:33 who is it uploading there? 15:27:39 someone uploads it to GCP (though we are working on moving away from fedimg to support automated updates) 15:28:15 jednorozec: I do it and I am also working on the package to do the automated uploads 15:29:28 so here is your image https://download-ib01.fedoraproject.org/pub/alt/unofficial/releases/36/x86_64/images/ 15:29:43 yes! Thank you. 15:29:51 the getfedora page source is little bit confusing for me 15:29:54 opening ticket there 15:33:52 davdunc[m, if you can ring a bell in the ticket we might get more attention and get it fixed https://pagure.io/fedora-web/websites/issue/250 15:35:31 ok, I dont have much more to discuss for today 15:37:38 Oh, I had one thing... 15:38:17 jednorozec: Done. 15:39:09 thanks 15:39:17 stage is your nirik 15:39:33 so, f34 and f35 container image updates have been failing for... ages. :( It's due to the weird bug with armv7 where it gets an old date on boot and can't fetch it's install files (because cert is invalid). I haven't really made any progress on fixing it or making a smaller reproducer. ;( So, I wonder... should we do a round of updates for those with armv7 dropped? at least the other arches would get updates that way. 15:39:47 I hate that they hvae 0 updates for months and people are using them 15:40:36 that sounds like a good idea 15:40:38 makes sense to skip the armv7 ones 15:41:16 +1 nirik 15:41:26 ok, I'll try and get that later today... 15:41:33 I wonder if people will notice. ;) 15:41:39 :) 15:44:00 so if that is all, I will close this meeting in few minutes 15:45:11 yeah, I don't think I have anything else... 15:49:47 #nedmeeting 15:49:52 #endmeeting