16:00:44 #startmeeting RELENG (2020-11-10) 16:00:44 Meeting started Tue Nov 10 16:00:44 2020 UTC. 16:00:44 This meeting is logged and archived in a public location. 16:00:44 The chair is mboddu. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:44 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:44 The meeting name has been set to 'releng_(2020-11-10)' 16:00:44 #meetingname releng 16:00:44 The meeting name has been set to 'releng' 16:00:44 #chair nirik sharkcz pbrobinson pingou mboddu dustymabe ksinny jednorozec 16:00:44 #topic init process 16:00:44 Current chairs: dustymabe jednorozec ksinny mboddu nirik pbrobinson pingou sharkcz 16:00:56 morning 16:02:05 รณ/ 16:04:20 * mboddu is in another meeting 16:04:25 I dont know why, but the timing of this meeting is always a problem 16:04:47 It is jinxed :( 16:05:56 hi all 16:07:47 #topic Alternate Arch Update 16:07:52 it's all daylight savings times fault. 16:07:53 sharkcz: Any updates? 16:08:06 nothing for today 16:13:50 Thanks sharkcz 16:13:53 #topic #9830 Bugzilla: Block the python, python2 and python3 components in Fedora Modules 16:13:59 #link https://pagure.io/releng/issue/9830 16:14:49 pingou: So, 'bugzilla modify -s NEW,ASSIGNED -c packagename -a orphan' is what we need to do? 16:15:56 hm 16:16:04 -p 'Fedora Modules' needs to be added as well 16:16:10 (never used the CLI so I wouldn't know) 16:16:17 mboddu: what about retiring all branches in PDC? 16:16:25 that should do the same things as maven's module 16:16:40 Okay, I could do it 16:16:50 prevents any further git push 16:16:53 Sure 16:16:56 our sync script should handle bz 16:16:58 Thats a better idea 16:17:14 hum. 16:17:39 what a suspens! 16:19:00 nirik:? 16:19:35 those are seemingly to me not to be open to new bugs already 16:19:38 * mboddu is confused 16:19:46 the links they show are old closed bugs? 16:20:09 * mboddu checks pdc entries 16:20:11 enabled for bugs [ ] (ie, not checked) 16:21:35 so possibly the toddler already closed them after those bugs were filed, (ie, this ticket is already done) 16:22:27 All the eol's in pdc are in the past 16:22:55 the best kind of ticket... "already done!" 16:23:33 * mboddu checking something 16:23:51 The latest EOL on them is '2019-05-28' so they are retired for more than an year 16:24:55 Okay, Miro retired them recently 16:25:10 So, yeah, it is "already done!" 16:26:29 #topic #9819 Toddlers fail to load ARM composes to PDC 16:26:32 https://pagure.io/releng/issue/9819 16:26:40 pingou: I think this is fixed now, right? 16:27:18 mboddu: yup 16:27:31 Thanks pingou 16:28:30 #topic #9794 permissions for carlwgeorge to implement epel-next proposal 16:28:35 #link https://pagure.io/releng/issue/9794 16:28:44 We started working on this with carlwgeorge 16:29:42 nirik: He needs bodhi sysadmin permissions only in stg for now if possible 16:30:25 I'm not sure how to do that in noggin. we will need to talk to the noggin team... 16:30:47 Not sure if *only staging* is possible as well 16:31:05 nirik: Yeah, I couldn't find any groups that I am part of in stg in noggin 16:31:27 I'm not sure how groups work, but we should find out! :) 16:37:13 #topic #9781 dist-git push (non-fatal) error 16:37:18 #link https://pagure.io/releng/issue/9781 16:37:29 pingou, nirik : Can we close this ticket? 16:38:18 oh yeah, that one... well, I think we still need a solution... 16:38:37 the short fix exists, the package isn't 16:38:52 so the next update will break it again if we forget to re-run the playbook 16:39:26 so in a 'normal' pagure deployment... this wouldn't matter? 16:39:41 it's just our crazy packager setup? 16:39:47 yup 16:40:06 and... 16:40:12 on pagure.io we don't have the issue 16:40:13 it should go away when we drop ssh pushes? 16:40:20 yup 16:41:03 so, perhaps we just live with it for now... although we should think about when we want to sunset ssh pushes. 16:41:11 +1 16:41:19 initiative worthy? 16:41:40 not sure. I wonder if it would be a good time when noggin rolls out to prod... 16:42:10 hm packagers will need an API token for git push over http 16:42:25 we haven't enabled them yet (though that should be fairly simple to do) 16:42:57 I'd like to figure a way to allow git push over http w/ kerberos but haven't took the time to look into it yet 16:43:49 So, two things here 16:44:04 it's enabled already I thought? 16:44:07 I use it all the time? 16:44:15 1. Close the ticket and hopefully we remember to run the playbook going further 16:44:22 using fedpkg? 16:44:52 https://fedoraproject.org/wiki/Infrastructure/HTTPS-commits ? 16:45:15 I always used ssh 16:45:32 potential next gen: https://docs.pagure.org/pagure/usage/http_push.html 16:47:13 * pingou needs to drop 16:47:22 Thanks pingou 16:47:41 nirik: the current way relies on fedpkg setting correctly the .git/config 16:47:56 the pagure built-in option does not, but relies on API token for our setup 16:47:59 right... 16:48:04 so we can consider both and pick the one we want 16:48:09 but you would have to get the token yourself and set it up or pass it 16:48:30 works headless :] 16:49:08 anyway, I've got to go 16:49:11 see you folks later! 16:49:19 sure, we can figure it out. bye pingou 16:49:30 mboddu: I guess I'd say we can close... 16:49:39 Okay, cool 16:50:21 FWIW, I like the API token approach 16:50:32 Anyway 16:50:38 #topic Open Floor 16:50:44 Anybody has anything to share? 16:51:29 not off hand 16:59:52 Okay 16:59:58 Thanks for joining 17:00:01 #endmeeting