15:01:39 #startmeeting RELENG (2020-03-10) 15:01:39 Meeting started Tue Mar 10 15:01:39 2020 UTC. 15:01:39 This meeting is logged and archived in a public location. 15:01:39 The chair is mboddu. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:39 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:39 The meeting name has been set to 'releng_(2020-03-10)' 15:01:40 #meetingname releng 15:01:40 #chair nirik sharkcz pbrobinson pingou mboddu dustymabe ksinny jednorozec 15:01:40 #topic init process 15:01:40 The meeting name has been set to 'releng' 15:01:40 Current chairs: dustymabe jednorozec ksinny mboddu nirik pbrobinson pingou sharkcz 15:01:48 hello 15:02:40 Hello 15:03:26 Hello everyone, welcome to the new scheduled time and the new channel 15:04:18 #topic #9297 Failure to push to forked src.fedoraproject.org repo 15:04:21 it's so new and shiny! 15:04:24 #link https://pagure.io/releng/issue/9297 15:04:47 so, I agree we need to improve docs/messages here. 15:05:33 I just haven't gotten back around to answer the stuff here or try and improve it. 15:06:51 they are also confused between pagure.io and src.fp.o in places... 15:07:22 nirik: One thing in the comments is, it seems https is not working on pagure.io? Why is it not working? 15:07:37 AFAIR, it was enabled in pagure.io way before on src.fp.o 15:07:53 https commits have never been accepted there I don't think? 15:07:55 s/on/than/ 15:08:32 Oh, I remembered that we enabled it on pagure.io first and then people brought up enabling it on src.fp.o 15:08:53 I might be wrong 15:09:41 I don't think we did that... but I also could be wrong. ;) we could ask pingou to respond to the ticket? 15:10:07 Sure, I will give it a try later 15:10:14 And I will take up the doc work 15:10:42 I think it will need some changes to pagure to be more clear about things too. 15:12:04 nirik: I think you are right, its not enabled on pagure.io 15:12:29 And sure, better explanation of pagure.io vs src.fp.o also helps 15:13:58 #topic #9154 F32 Change: new buildroot for CPU baseline update 15:14:05 #link https://pagure.io/releng/issue/9154 15:14:20 nirik: We got pinged about it just now, so, I decided to talk about it :) 15:14:44 yeah,again, I saw it and just haven't had time to go back to reply 15:16:17 for signing we would need to add another tag I guess... 15:16:43 also koji-gc likely needs adjusted if they are going to tag in rawhide packages. 15:17:13 Yes, but why all arches? Since the change only talks about x86_64 15:17:47 dunno, perhaps there's work to enable those changes in other arches? 15:18:04 I guess it wouldn't hurt to give them all the arches 15:18:45 also, we need to adjust/write policy to allow them to manage things. 15:18:50 And we need to check how they are planning to use it and why would they need signing? 15:19:06 Yes, esp it seems like they want to tag stuff 15:19:16 and add packages 15:19:28 Yes 15:19:38 I will ask those two questions and then I will pick up the work 15:19:46 Any objections on the naming? 15:19:48 I guess they want signing just for integrety/etc. 15:19:56 seems fine to me, don't care. ;) 15:19:57 eln? 15:21:03 they are planning to make test composes... signed packages will make sure they are all from the known source, etc... 15:21:44 also, one final thing... I wonder what the desired timeframe is... because it might be best for us to do after the datacenter move. Or at least ask them to not do a bunch of builds while we are moving. 15:22:20 Right, also whether they can complete it in f32 or they need them for f33? 15:22:43 And I am not a big fan of giving signing for the repo that we are not going to ship 15:23:38 well, thats a good question... is there an end/done state... 15:24:21 sounds like they are not set on signing if you want to not do that we could 15:25:54 I just worry about test composes wandering around with unsigned packages... might make someone make some fake ones... 15:27:23 Hmmm, "cryptography", enabling means people think they are real repos, disabling means people can make fake repos 15:30:04 I know! odcs can sign repodata! 15:30:07 * nirik runs far away 15:30:14 What? 15:30:33 That might confuse people 15:30:35 Oh well 15:30:43 signing repodata (like the h264 repo) is horrible... it's confusing and the interface is bad 15:30:49 so it was a joke. ;) 15:31:16 Haha :) 15:31:26 #topic #9226 texlive makes koji sad (and traceback) 15:31:34 #link https://pagure.io/releng/issue/9226 15:31:46 nirik: Can you deploy koji 1.20.1? 15:31:57 I guess we should wait for freeze 15:32:01 I sent a freeze break yesterday for that... 15:32:07 but sent it to the wrong address. ;) 15:32:10 just resent it 15:32:28 I think it should be pretty safe to do in freeze... there's no db changes... 15:32:43 it's all just bugfixes 15:32:52 Okay, I +1'd it 15:34:42 thanks 15:35:15 #topic #8948 Update list of critpath packages 15:35:21 #link https://pagure.io/releng/issue/8948 15:35:58 this is done? or no? 15:36:02 https://pagure.io/releng/pull-request/9284 should fix this 15:36:09 But I ran it manually last time 15:36:16 We should make it a cron or something 15:36:27 There is no cron job set up for it 15:36:55 well, it might be tricky, it needs a pdc token... 15:37:19 Nightly compose generates the critpath list, but nothing setup to upload them to pdc 15:37:28 Yes, which is why I brought it up 15:37:38 I uploaded it manually using my token 15:37:42 yeah 15:38:01 a cron or something would be good... 15:38:59 One thing is, maybe we can create a releng token for pdc and use it in one of the compose boxes, or use the token in pdc-backend01 15:39:35 yeah, needs investigation 15:39:55 Okay 15:41:22 I guess keep this ticket open to track? or close and do a new one? 15:42:34 I am keeping the ticket and just commented on it 15:42:55 ok 15:44:13 #topic #8919 When releng unorphans (or unretires) packages, it should reassign bugzillas (or ask the packagers) 15:44:20 #link https://pagure.io/releng/issue/8919 15:44:38 * nirik reads this one 15:45:11 I want to know how to assign the bz component to someone 15:45:36 I thought our script would do this... 15:45:54 Thats what I thought 15:46:03 Seems like its not doing it sometimes 15:46:35 well, it was recently re-written, we should check with pingou on it. 15:46:58 but to reassign, just go to the bug, change asignee... or did you mean command line/en mass? 15:47:24 nirik: Mass update, either on web ui or cli 15:48:43 should be easy on command line... bugzilla modify -s NEW,ASSIGNED -c packagename -a 15:48:45 or something like that 15:49:15 but I think we should see if the cron/script can do it... to avoid issues. 15:50:20 definitely 15:50:27 We could check with pingou later 15:50:36 But that helps me for now 15:50:38 I added a question to him in the ticket. 15:51:10 Thanks 15:51:15 #topic Open Floor 15:52:25 * nirik has nothing off hand 15:53:45 Well, we have F32 Beta scheduled for release next week 15:53:57 Which I think is not going to happen looking at blocker bugs and stuff 15:54:43 yeah, hard to say... 15:54:54 but not looking great 15:56:18 And the schedule doesn't have preferred and final targets dates for f32 beta 15:56:58 odd. 15:57:05 should ask bcotton about that 15:57:26 And I am not seeing bcotton anywhere 15:57:30 Maybe he is traveling 15:58:40 I think he was at scale? might be traveling back 15:59:32 I pinged him on FB 15:59:53 Desperate times calls for desperate measures :P 16:00:38 Okay, thats it guys, thanks everyone for joining 16:00:54 #endmeeting