19:00:00 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 19:00:00 Meeting started Mon Nov 30 19:00:00 2020 UTC. 19:00:00 This meeting is logged and archived in a public location. 19:00:00 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:00 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:00:00 #chair mboddu nirik smooge pingou mobrien 19:00:00 #meetingname fedora_infrastructure_ops_daily_standup_meeting 19:00:00 #info meeting is 30 minutes MAX. At the end of 30, its stops 19:00:00 Current chairs: mboddu mobrien nirik pingou smooge 19:00:00 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 19:00:01 #info agenda is at https://board.net/p/fedora-infra-daily 19:00:02 #topic Tickets needing review 19:00:03 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 19:00:09 * nirik waves 19:00:19 damn it 19:00:24 my paste was too slow 19:00:46 * mboddu is here 19:00:46 oh sorry, didn't mean to mess you up 19:00:58 * linuxmodder here lurking 19:01:18 .ticket 9495 19:01:19 nirik: Issue #9495: Mailing list admin - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9495 19:01:26 just needs doing, low/low/ops? 19:01:40 or we could just do it 19:01:49 well what needs doing? 19:01:52 remove the spam? 19:01:56 close the list? 19:02:15 give the person admin? 19:03:00 give the person admin. I did it. We could also nuke spam? 19:03:39 nuked 19:04:03 .ticket 9497 19:04:04 nirik: Issue #9497: unable to open pull request for "packaging-committee" - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/9497 19:04:06 dang it I am slow 19:04:16 thanks nirik 19:04:27 I guess low/low/ops or low/low/dev? 19:04:34 waiting on info from the reporter 19:05:01 low/low/dev waiting on info from reporter 19:05:02 +1 19:05:03 +1 19:05:07 sure 19:05:15 thats it on infra... mboddu: any releng? 19:05:21 Yep 19:05:43 Lets do couple of them at once 19:05:50 .releng 9868 19:05:51 mboddu: Issue #9868: Unretire rpms/python3-cffi (EPEL only) - releng - Pagure.io - https://pagure.io/releng/issue/9868 19:05:55 and 19:06:01 .releng 9871 19:06:02 mboddu: Issue #9871: Unretire rpms/emacs-lua - releng - Pagure.io - https://pagure.io/releng/issue/9871 19:06:07 Both, low, low, ops 19:06:10 +1 19:06:46 .releng 9866 19:06:47 mboddu: Issue #9866: F34 self contained change: kasumi-unicode - request for review - releng - Pagure.io - https://pagure.io/releng/issue/9866 19:07:33 low, low, ops 19:08:07 +1 19:08:10 +1 19:08:37 .releng 9867 19:08:38 mboddu: Issue #9867: RFE: data store and/or messages and/or server for release cycle information - releng - Pagure.io - https://pagure.io/releng/issue/9867 19:09:03 This is med (or high) trouble, high gain, dev+ops 19:09:36 Sure. And adamw already implemented it. 19:10:26 Yeah, but it needs to be deployed somewhere in infra, it also needs some improvements and probably a config to store those values and so on... 19:10:46 Thats why I think its at least med trouble 19:10:47 and it needs to be maintainable 19:10:54 Yep 19:10:56 yes, it's not a slam dunk 19:11:08 So, med or high trouble? 19:11:44 either... I'd lean to high 19:11:56 high 19:12:52 Okay, high it is 19:13:24 .releng 9869 19:13:26 mboddu: Issue #9869: Add aarch64 to the koji container tag for f32, f33 for production and staging - releng - Pagure.io - https://pagure.io/releng/issue/9869 19:13:34 This is low, low, ops 19:13:53 I already updated the stg but I am not sure if we should enable it for prod yet, which is what I asked the requestor 19:14:09 I think they did deploy in prod, but not sure it's working there. 19:14:57 Okay 19:15:21 .releng 9872 19:15:22 mboddu: Issue #9872: Create detached signatures for the Ignition 2.8.0 release - releng - Pagure.io - https://pagure.io/releng/issue/9872 19:15:30 low, low, ops as well 19:15:33 ? 19:15:38 +1 19:16:16 And the last one 19:16:19 .releng 9873 19:16:20 mboddu: Issue #9873: Unable to rebuild filezilla in epel8 due to lack of requires on pkgconfig(libuv) - releng - Pagure.io - https://pagure.io/releng/issue/9873 19:16:56 Not sure if it is ever fixable or not 19:17:02 thats due to the centos Devel repo not updated yet for 8.3 I think 19:17:49 Oh I thought its not shippable at all 19:17:54 * mboddu checks something 19:17:59 I am pretty sure thats one of the ones in Devel 19:19:01 anyhow, either close with 'wait for centos Devel' ? 19:19:50 +1 to close it and let them know waiting on centos devel 19:20:45 Thats all I got 19:20:52 ooh 19:21:04 oof is what I meant to write 19:21:14 cool. 19:21:16 yeah close with predjudice 19:21:24 Any other ones to discuss / blockers / prs? 19:21:37 None from me 19:21:47 no I am working on EOL F31 and El6 and working with puiterwijk on dns 19:21:51 note that I think smooge is out friday. 19:22:02 smooge is out on fridays for the rest of the year 19:22:14 I'm going to try and get builders updated to f33 this week... 19:22:16 Oh, I got a question to nirik 19:22:20 puiterwijk is also out on fridays for the rest of the year. (not that it's important to this meeting :D) 19:22:52 puiterwijk is out on Friday's but his clones will work 24*7 through out the year ;P 19:22:55 nirik, oh there was an outage this morning on a bvmhost-a64 box this morning. The builders xml all needed to be hand edited to run afterwords 19:23:00 I'm here for the next 2 fridays, then I am out until jan 4th. 19:23:45 smooge: yeah, it changed in 8.3... I hope tho we can move armv7 is uefi... thats the last thing I was waiting for 19:23:52 nirik: So, is there any reason why the signed rpms are not removed for epel 5? 19:24:14 I am looking at removing epel6 signed rpms and found that epel5 stuff are still around 19:24:32 removed from where? 19:24:52 mboddu: not really, but I'd say we should adjust koji-gc to do it, not do anything manually? 19:25:18 smooge: On /mnt/koji/, we generally remove signed copies of the rpms when a release goes EOL 19:25:40 I didn't run EOL on epel5, hence the question 19:26:14 it should prune the old ones. So we should fix that 19:26:18 nirik: We have to run it manually at EOL since there is no way of saying to koji-gc to remove them "on this date" 19:27:38 mboddu: it should remove all them that aren't protected tho? 19:28:52 I don't see epel5/6 as protected... 19:29:04 anyhow, we should figure it out... out of meeting? 19:29:13 nirik: Okay, but we could add 'age' to the koji gc policy 19:29:17 Yeah 19:29:20 But thats all I got 19:29:26 age defaults to 5 days 19:30:26 ok, thanks for coming everyone... 19:30:29 #endmeeting