18:00:10 <nirik> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting
18:00:10 <zodbot> Meeting started Thu Jun 10 18:00:10 2021 UTC.
18:00:10 <zodbot> This meeting is logged and archived in a public location.
18:00:10 <zodbot> The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:10 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:10 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:11 <nirik> #chair mboddu nirik pingou mobrien nb
18:00:11 <zodbot> Current chairs: mboddu mobrien nb nirik pingou
18:00:11 <nirik> #meetingname fedora_infrastructure_ops_daily_standup_meeting
18:00:11 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:11 <nirik> #info meeting is 30 minutes MAX. At the end of 30, its stops
18:00:11 <nirik> #info agenda is at https://board.net/p/fedora-infra-daily
18:00:11 <nirik> #info reminder: speak up if you want to work on a ticket!
18:00:13 <nirik> #topic Tickets needing review
18:00:17 <nirik> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
18:00:17 <nb> Hi!
18:00:28 <mboddu> Hello
18:00:55 <nirik> morning
18:01:09 <nirik> .ticket 10026
18:01:10 <zodbot> nirik: Issue #10026: access to sysadmin-releng - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10026
18:01:20 * eddiejennings waves.
18:01:24 <nirik> this just needs doing... mboddu is the only sponsor, so I will leave it to him.
18:02:38 <mboddu> Okay, I will take it
18:02:53 <nirik> .ticket 10027
18:02:55 <zodbot> nirik: Issue #10027: Cannot setup mirroring from pagure to github - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10027
18:03:04 <nirik> no idea on this one, low/low/ops?
18:03:29 <mboddu> If no idea, then doesn't it mean med/med/ops?
18:03:35 <nirik> actually, let me check something.
18:03:37 <nirik> sure,
18:04:40 <mboddu> `Private key not found on disk, bailing.` maybe thats whats the problem is?
18:05:45 <nirik> yeah, ok, I don't know enough about how it's setup to say.
18:06:23 * mboddu neither
18:06:31 <mboddu> Anyway, updated to med/med/ops
18:06:56 <nirik> ok, thats it on infra
18:07:00 <nirik> releng?
18:07:31 <mboddu> Yup
18:07:46 <mboddu> .releng 10160
18:07:47 <zodbot> mboddu: Issue #10160: RFE in failed-composes list the DOOMED resons first - releng - Pagure.io - https://pagure.io/releng/issue/10160
18:07:59 <mboddu> high,high,dev?
18:08:21 <nirik> or should this be refiled on compose-tracker?
18:08:56 <mboddu> Sure, that is an option, but its gonna be either jednorozec or me working on it, so it doesn't matter where its tracked
18:09:06 <nirik> sure, whatever works.
18:09:20 <nirik> I'm not sure it's really high gain... but whatever
18:09:49 <mboddu> But I am thinking of filing a RFE for pungi to provide that info in pungi.global.log, that would make it very simple
18:10:20 <mboddu> .releng 10161
18:10:21 <zodbot> mboddu: Issue #10161: `fedpkg container-build` says "malformed task" - releng - Pagure.io - https://pagure.io/releng/issue/10161
18:10:35 <mboddu> Not sure whats going on
18:10:45 <mboddu> Its OSBS stuff
18:10:58 <nirik> yep.
18:11:11 <nirik> we could try blindly restarting... but also it might be something broke with new koji
18:11:30 <mboddu> I dont even know how to restart OSBS :(
18:11:39 <mboddu> I should get a quick demo of it from David
18:11:49 <mboddu> So, med/med/ops and ping David?
18:11:49 <nirik> it's basically just an openshift cluster.
18:11:55 <nirik> sure.
18:12:04 <nirik> cverna might also know?
18:13:31 <nirik> the bug may be in the koji plugin
18:13:33 <mboddu> Yeah, but cverna given that task to David and Vipul
18:14:25 <mboddu> .releng 10162
18:14:26 <zodbot> mboddu: Issue #10162: Are repos in the container namespace also branched from rawhide? - releng - Pagure.io - https://pagure.io/releng/issue/10162
18:15:30 <mboddu> We dont branch container namespace, we thought it will be up to the maintainers whether to branch it or not
18:15:36 <nirik> yeah.
18:15:40 <mboddu> Maybe we should revisit and file FESCo ticket?
18:16:11 * nirik shrugs.
18:16:23 <nirik> I'm really not sure how much those are really used.
18:16:27 <nirik> (that might be nice to know)
18:16:56 <mboddu> At least, lets visit in next releng meeting and figure out the details
18:17:15 <mboddu> For now, its med/med/ops
18:18:12 <mboddu> ?
18:18:30 <nirik> sure
18:20:22 <nirik> any others?
18:21:49 <mboddu> Thats all
18:23:24 <nirik> #topic upcoming plans
18:23:56 <eddiejennings> I realized I missed the weekly meeting :(.  I have a quick question about PRs.
18:24:01 <nirik> anything special upcoming? I got the wiki upgrade working in stg, but auth is still broken... once thats fixed I can schedule doing prod
18:24:13 <nirik> eddiejennings: fire away
18:24:27 <eddiejennings> I know fixes for something should have their own branch.  Would you do a single PR for each branch, or is there a way of including several branches on one PR?
18:25:28 <nirik> one pr per branch normally.
18:25:36 * eddiejennings nods.
18:25:38 <nirik> I am not sure it's possible to do a single pr from multiple branches.
18:25:50 <nirik> you can of course do multiple commits on the same branch
18:25:50 <mboddu> eddiejennings: One PR ber branch, but you can reuse the branch as long as you rebase that branch from the upstream repo
18:25:57 <nirik> that too
18:26:25 <mboddu> I am 100% positive that one cannot create a PR from multiple branches
18:26:47 <eddiejennings> There it is then :)
18:27:32 <nirik> oh, I will likely be out shopping/running errands tomorrow afternoon. Still also need to find a time to do my keyboard replacement.
18:28:03 <nirik> #topic Discussion / Open Floor
18:28:08 <nirik> anything else to discuss?
18:28:26 <mboddu> nirik: I know you have lot of headset problems, but if you have any wired headset problems https://koji.fedoraproject.org/koji/buildinfo?buildID=1767851 helped me
18:28:28 <eddiejennings> Nothing from me.  Other than I've added weekly meeting to my calendar so I'll get a reminder next time
18:28:31 <darknao> speaking of PR
18:28:32 <mboddu> So, I packaged into Fedora :D
18:28:53 <darknao> if someone can take a look to #632, that would be awesome
18:29:03 <mboddu> darknao: Which repo?
18:29:04 <nirik> mboddu: all bluetooth here (well, I have one usb one, but I don't use it much)
18:29:12 <darknao> https://pagure.io/fedora-infra/ansible/pull-request/632
18:29:46 <nirik> darknao: I wasn't sure the order of those ones... but they all looked fine to me.
18:29:53 <darknao> PR on fedora-website have been merged already
18:30:02 <darknao> and without this one, build are not working anymore
18:30:23 <darknao> because of missing langtable package
18:30:37 <nirik> 613 , 615, and 632
18:30:46 <nirik> oh, and 604
18:30:56 <darknao> yeah, i'm all over the place :p
18:31:21 <nirik> I can just merge em all if they are ready... one has WIP still tho
18:31:28 <mboddu> darknao: If you are splitting #613, then can you close it?
18:31:55 <darknao> 613 has to wait for another PR on website side
18:32:09 <darknao> i'll rebase it with only prod stuff in it soon
18:32:34 <nirik> ok, so shall I merge 604, 615 and 632 then?
18:32:43 <darknao> all others can be merged
18:32:50 <mboddu> Yeah, but if #632 is merged, then #615 will be redundant, right?
18:32:52 <nirik> and can you do playbook runs? or did you need me to do sundries?
18:33:42 <darknao> 615 and 632 are not about the same component
18:34:09 <darknao> one is for website building, the other one is for website translation
18:34:25 <darknao> they are related to the same issue tho
18:34:34 <mboddu> Ah okay
18:34:40 <darknao> nirik: no i can't run any playbook
18:34:45 <nirik> ok, we are over time... lets continue in normal channels.
18:35:07 <nirik> darknao: I thought we set you up to run some. ok, I can run them...
18:35:12 <nirik> #endmeeting