18:05:00 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:05:00 Meeting started Wed Mar 16 18:05:00 2022 UTC. 18:05:00 This meeting is logged and archived in a public location. 18:05:00 The chair is nirik. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:05:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:05:00 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:05:00 #chair mboddu nirik mobrien nb 18:05:00 Current chairs: mboddu mobrien nb nirik 18:05:00 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:05:00 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:05:00 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:05:00 #info agenda is at https://board.net/p/fedora-infra-daily 18:05:01 #info reminder: speak up if you want to work on a ticket! 18:05:03 #topic Tickets needing review 18:05:05 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:06:26 .ticket 10587 18:06:27 nirik: Issue #10587: No F36 upgrade data available for F34 and F35 - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10587 18:07:06 Why isn't F36 available for F34? 18:07:12 I'm not sure why this is happening now. 18:07:17 it should be. 18:07:18 Something in gnome-software? 18:07:31 dunno. we can ask for debug logs. 18:07:34 * mboddu hopes its not another blocker 18:08:07 I'll ask, we can move it to med/med ops? 18:08:25 +1 18:08:29 I will update the tickets 18:08:33 oh I guess it just needs status changed 18:08:43 can you ask them for gnome-software --verbose logs? 18:08:51 Yeah 18:09:08 .ticket 10595 18:09:09 nirik: Issue #10595: Outage: Upgrade of Copr servers - 2022-03-21 08:15 UTC - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10595 18:09:15 low/low/ops/outage? 18:09:43 +1 18:10:45 So that leaves releng tickets? 18:11:11 yep 18:11:11 hello. sorry for the delay 18:11:16 hey smooge 18:11:25 Hello Smooge 18:11:26 i will be interested in the fix 18:11:37 .releng 10697 18:11:38 mboddu: Issue #10697: problem creating repo. bug creator didn't match requester in Pagure - releng - Pagure.io - https://pagure.io/releng/issue/10697 18:11:57 Well jednorozec already mentioned the issue here, close it? 18:12:36 I guess... 18:13:47 .releng 10699 18:13:48 mboddu: Issue #10699: Please send openh264-2.2.0-1.fc37, openh264-2.2.0-1.fc36 and openh264-2.2.0-1.fc35 to Cisco - releng - Pagure.io - https://pagure.io/releng/issue/10699 18:14:00 med, med, ops and I need to run it with jednorozec 18:14:25 +1 18:14:50 .releng 10700 18:14:50 mboddu: Issue #10700: Stalled EPEL package: xmlstarlet - releng - Pagure.io - https://pagure.io/releng/issue/10700 18:14:53 low, low, ops 18:15:09 +1 18:15:23 .releng 10701 18:15:24 mboddu: Issue #10701: epel8-next builds using libusbmuxd-devel fail due to hash change - releng - Pagure.io - https://pagure.io/releng/issue/10701 18:15:37 Maybe two entries with different hashes? 18:15:46 For now low, low, ops? 18:15:51 And nirik can you take care of it? 18:16:16 I can look. 18:16:30 never Ebeneezer_Smooge mentioned something 18:16:31 I am going to push back on modifying the db if I can tho. that's very fragile. 18:16:37 Seems like a bigger bug 18:16:52 Thats why I give those tasks to you :) 18:17:29 nirik, I am expecting it is a duplicate in the db but as you said it is a fragile problem that needs upstream to fix 18:18:14 I am marking it med, med, ops because of its fragility 18:18:34 That is all from releng 18:18:36 i checked the ondisk rpm and the hash value is the one which koji is complaining about. It hasn't changed since december 18:19:30 it's because: 18:20:01 it's in rhel8-base external repo and centos-stream-8 external repo 18:20:07 with different hashes 18:20:18 I see that was the same exact package we had a problem with "Issue #10381: EPEL8 builds using libusbmuxd-devel fail due to hash change" 18:20:46 why is rhel8-base being looked at for epel-next? 18:21:47 because epel8-next inherits from epel8 18:22:10 ah.. 18:22:28 well I expect then that is going to be broken over and over again then 18:22:29 I'm not sure what to do here... but we can discuss out of meeting. 18:22:32 yep 18:22:33 yep 18:22:35 And that design is because of the same pkg list 18:22:47 Yeah, lets talk about it later 18:22:51 Anyway, that is all 18:23:03 #topic Planning / Upcoming work 18:23:16 #info .ie has holidays tomorrow/friday 18:23:24 #info f36 beta freeze still in effect 18:23:28 Waiting for RC, openh264 and things as they come 18:24:08 Yeah, I'm trying to whittle down my backlog some, but been also a bit under the weather so not going super fast. ;) 18:24:23 #topic Discussion / AOB 18:24:27 anything to discuss? 18:24:35 Oh, I hope you will feel better soon nirik 18:24:39 Nothing from me 18:24:59 Likewise. and recover quick nirik 18:26:38 thanks. It's not horrible, just a bit of a cough and a malaze 18:26:46 Thanks for coming everyone! 18:26:49 #endmeeting