15:00:03 #startmeeting RELENG (2022-09-20) 15:00:03 Meeting started Tue Sep 20 15:00:03 2022 UTC. 15:00:03 This meeting is logged and archived in a public location. 15:00:03 The chair is jednorozec. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 15:00:03 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:03 The meeting name has been set to 'releng_(2022-09-20)' 15:00:03 #meetingname releng 15:00:03 The meeting name has been set to 'releng' 15:00:03 #chair nirik sharkcz pbrobinson phsmoura dustymabe jednorozec 15:00:03 #topic init process 15:00:03 Current chairs: dustymabe jednorozec nirik pbrobinson phsmoura sharkcz 15:00:10 morning 15:00:13 morning 15:00:17 hello 15:01:24 I dont have anything prepared for today 15:01:38 we can go through tickets 15:01:46 sure. 15:03:04 I think we can now close https://pagure.io/releng/issue/6967 provided my docs pr got merged. 15:03:27 I think I merged it 15:03:33 so yeah lets close 15:03:39 yep. Looks like it has been. 15:03:45 you got it, or shall I? 15:03:53 I can 15:05:21 I was thinking about https://pagure.io/releng/issue/11039 15:05:39 * nirik reads. 15:05:47 sounds like they are trying to connect as root? 15:05:57 oh wrong ticket :) 15:05:59 but yeah 15:06:09 I think they dont even have ssh key in fas 15:06:11 let me comment 15:06:34 this one was the one I was thinking about 15:06:35 https://pagure.io/releng/issue/10847 15:06:48 I dont see how we can catch this 15:07:00 they need to login to sync their group membership and ssh key, then not clone as root. ;) 15:07:05 maybe we can ask for confirmation if there are numbers in the name? 15:08:01 yeah, I guess it might be impossible... 15:09:04 could we check against the .spec in the bug? 15:09:11 hmm 15:09:26 that complicates things but it will work 15:09:40 because the project should == the name in the spec file. 15:10:04 right 15:10:31 Checking the specfile will work 15:12:00 yeah, complicated, but possible I think 15:12:26 I wrote comment and pinged michal on the ticket 15:12:59 cool 15:13:42 what about this one 15:13:47 .releng 10911 15:13:48 jednorozec: Issue #10911: EPEL8/ELN Modular builds are failing - releng - Pagure.io - https://pagure.io/releng/issue/10911 15:14:39 I think that was solved... 15:14:45 not 100% sure. 15:14:57 (also theres a epel proposal to drop modules in epel8) 15:15:23 that would be nice 15:15:56 so, we could close this one and ask them to reopen if they see any further issues? 15:16:08 * jednorozec is writing the comment right now 15:17:54 nex one 15:17:57 .releng 10913\ 15:17:57 jednorozec: Error: '10913\\' is not a valid integer. 15:17:59 .releng 10913 15:18:00 jednorozec: Issue #10913: untag nextcloud modules from epel8-modular-updates - releng - Pagure.io - https://pagure.io/releng/issue/10913 15:18:36 I have untagged the builds 15:20:59 closing as fixed 15:21:19 +1 15:22:21 .releng 10765 15:22:22 jednorozec: Issue #10765: secure boot signing for systemd-boot - releng - Pagure.io - https://pagure.io/releng/issue/10765 15:23:34 this seems to have stalled out... not sure where it is. 15:24:18 I see empty repo with no branches https://src.fedoraproject.org/rpms/systemd-boot 15:24:33 ok, so it's not been imported yet... 15:25:17 so, I would say leave it for now... 15:25:26 +1 15:25:44 https://pagure.io/releng/issue/9689 we asked on 2 months ago... perhaps we can close that one now? 15:26:05 closing 15:27:04 .releng 10369 15:27:05 jednorozec: Issue #10369: Q: Why do we install epel-release and fedpkg-minimal into every buildroot in Koji? - releng - Pagure.io - https://pagure.io/releng/issue/10369 15:27:25 so I see my comment on there but I dint test it :/ 15:28:16 note: koji prod->stg is syncing now. :) I had to do it because I accidentally triggered a failed sync yesterday. ;( 15:28:47 https://pagure.io/releng/issue/11037 can be closed I think. phsmoura made pr's and I merged them... 15:29:23 phsmoura, since you did the work do you want to close it? 15:29:31 sure 15:30:12 done 15:30:35 👍🏻 15:30:38 awesome 15:30:58 .releng 10663 15:30:59 jednorozec: Issue #10663: Clean, or Remove epel8-playground repo - releng - Pagure.io - https://pagure.io/releng/issue/10663 15:31:18 was this fixed alredy or is the repo there 15:31:56 https://dl.fedoraproject.org/pub/epel/playground/8/ 15:32:14 it's still there. I don't like the idea of removing it... I'd prefer if we could move it to archive. 15:32:46 so same steps as moving fedora release to archive? 15:33:14 yeah, similar I would think, except instead of copying... move. 15:33:31 could just go do it now... 15:33:54 go for it please 15:36:05 need to find a machine that has archive and epel. ;) just a sec. 15:37:56 moving 15:38:50 huh, https://pagure.io/releng/issue/11039#comment-817316 15:39:08 wonder how big it is... still moving 15:39:13 have you seen something like that? 15:40:04 weird. not that I recall... 15:40:15 ok, playground is moved. 15:40:19 I think they might be using pip packages with system ones 15:40:32 nirik, awesome will you comment on that ticket? 15:40:41 yep. 15:40:59 if it ever loads. come on pagure... 15:41:45 done 15:43:40 there's a lot of f37 changes... but I guess we close those later? 15:44:09 yeah later, I prefer doing it after go meeting 15:45:10 ok 15:45:52 did you have a chance to look into https://pagure.io/releng/issue/11006 any? 15:46:21 the paste expired, so I am not sure the messages. ;( 15:46:53 aww 15:47:39 so there were no tags for f34+ in quay 15:47:47 anyhow, I guess it needs more digging 15:47:58 ah, that would somewhat do it 15:48:18 let me check if it kicked in 15:49:57 yeah I need to dig little bit more 15:50:04 sounds good. 15:50:47 * nirik needs to go feed cats soon. There's one yelling at me. ;) 15:50:48 but I remember updating the docs so we create new tags after branching 15:51:27 ok I will have to drop as well 15:51:43 we are at 77 tickets 15:51:50 probably the lowes I have seen so far :) 15:53:15 we are definitely making progress. ;) 15:53:30 ok I will close the meeting. 15:53:33 have a nice day 15:53:36 #endmeeting