18:00:08 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:08 Meeting started Mon Jun 14 18:00:08 2021 UTC. 18:00:08 This meeting is logged and archived in a public location. 18:00:08 The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:08 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:08 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:08 #chair mboddu nirik pingou mobrien nb 18:00:08 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:00:08 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:08 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:08 Current chairs: mboddu mobrien nb nirik pingou 18:00:08 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:08 #info reminder: speak up if you want to work on a ticket! 18:00:10 #topic Tickets needing review 18:00:12 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:02:03 I am here 18:02:14 hey mboddu 18:03:26 .ticket 10028 18:03:27 nirik: Issue #10028: Gitlab Fedora Namespace: Cybersquatting request - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10028 18:03:41 this is just a fyi thing... just mark it waiting on external? 18:04:29 Okay 18:04:52 No other tags? low/low/ops? 18:05:03 no, because it's not something we are going to do? 18:06:08 I mean you can and we can ignore it, but it seems to me to just mark it waiting for external and leave it alone. 18:06:50 Okay 18:07:48 .ticket 10031 18:07:49 nirik: Issue #10031: Deploy the rpmautospec builder plugin to Koji in prod - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10031 18:07:49 HHi 18:08:04 med/med/ops ? I've not looked at the pr yet. 18:08:07 hey nb 18:09:36 o/ 18:10:00 ack 18:12:28 .ticket 10032 18:12:29 nirik: Issue #10032: lenkaseg needs to become a member of https://github.com/fedora-infra - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10032 18:12:45 I can do this, need to confirm with them what their github id is... 18:12:50 low/low/ops? 18:13:07 +1 18:13:43 FYI, this is someone who is joining the CPE team as a intern and have done work on pagure in the past... so they aren't just coming from nowhere. ;) 18:14:29 thats it for infra. any releng ones? 18:15:15 nirik: intern? I thought she is joining as associate software engineer? 18:15:40 On releng side, there was one and I closed it already :D 18:16:39 oh, perhaps I am confused and am mixing up who is who 18:16:49 yeah, sorry about that... 18:18:35 :) 18:18:48 #topic work plans / upcoming tasks 18:18:49 #info everyone should note what things they are hoping to work on over the next day/week 18:19:16 I'm still wanting to get macos notorizing working, but It looks like I will need to make a new apple account... :( 18:19:28 then I plan to fight down tickets again 18:19:48 upgrading proxies to f34 sometime 18:20:00 nirik: Please document the process so that when I get access my mac hardware, I can help you as well 18:20:01 and I have a bunch of random packaging work to catch up on 18:20:17 Oh right, I need to update my packages as well 18:20:36 mboddu: sure, the process itself is easy... but I need to setup a app specific pass for it, which I can't do on our current account because I can't get in fully. ;( 18:21:25 fedora-release has a bunch of random bugs we should go thru sometime. 18:21:37 jednorozec: ^ When you get a chance, can you looking at converting the windows cert or probably add the cert to the private repo 18:21:55 Yup, which is on my list 18:22:15 I am mostly working on CS stuff this week 18:22:23 Mass rebuild in CS, interesting... :D 18:22:37 cool. let me know if I can help any. 18:22:44 #topic Discussion / AOB 18:22:48 mboddu, will do it first thing tomorrow 18:22:49 anything to discuss further? 18:23:06 Nope 18:23:23 Double negation ^ to that 18:23:29 I have couple of questions 18:23:48 nirik: Can you prioritize https://pagure.io/fedora-infrastructure/issue/10027 ? 18:24:00 * nirik sighs. 18:24:16 I am not sure how to debug it 18:24:20 I am not sure anyone knows the setup besides pingou 18:24:37 I can take another look... 18:24:48 nirik: Hmmm, you and me on same boat then :( 18:24:52 but failing that I am not sure how we can prioritize it. 18:25:18 and I already had a google chat and updated the ticket this morning, so I guess it's sure blocking something. 18:26:28 Hmmm, lets try debugging it, if we cannot find a solution, we will ping pingou in the ticket (I know its terrible) and leave at it for his response 18:27:05 ok 18:27:14 2nd question: 18:27:36 nirik: Where are the logs stored for koji gc? Both regular gc and pruned signed copies? 18:28:07 releng-cron mailing list has all output from the gc jobs 18:28:15 pruned signed copies cron send an email to releng-cron, but I am not able to find python-sqlalchemy-collectd-0.0.4-9.eln112 in there 18:28:56 But its signed copy was removed 18:29:27 I would think it would be... 18:29:37 if not it would be in the journal on koji02? 18:29:54 koji-gc service doesn't have any journal log 18:30:38 it's a cron job. 18:30:59 I don't know why it wouldn't output that if it pruned it. 18:32:26 It happened with only the srpm builds, so something is set with srpm's thats getting pruned 18:33:06 weird 18:33:24 might be a bug in the pruned signed copies 18:33:55 ok, we are over time... anything else to discuss? 18:34:15 None from me 18:35:01 cool. thanks everyone. 18:35:04 #endmeeting