18:00:15 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:00:15 Meeting started Mon Mar 23 18:00:15 2020 UTC. 18:00:15 This meeting is logged and archived in a public location. 18:00:15 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:15 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:15 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:00:15 #chair cverna mboddu nirik smooge 18:00:15 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:00:15 Current chairs: cverna mboddu nirik smooge 18:00:15 #info agenda is at https://board.net/p/fedora-infra-daily 18:00:15 #topic Tickets needing review 18:00:17 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:00:24 morning 18:00:35 .ticket 8765 18:00:36 nirik: Issue #8765: Issues with SSO on websites - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8765 18:00:42 Hola 18:00:46 Morning nirik 18:00:56 so, this is a known thing I think with windows. I am not sure there's any workaround. 18:01:12 I added it to the faq. Perhaps we could ask puiterwijk if there's any hope to fix it... 18:01:46 I'd say close can't fix, sorry... tell people to cancel if they get a windows dialog. 18:01:50 * cverna says hello 18:02:18 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8765: authentication, high-trouble, and low-gain https://pagure.io/fedora-infrastructure/issue/8765 18:02:19 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8765 https://pagure.io/fedora-infrastructure/issue/8765 18:02:19 .ticket 8767 18:02:20 nirik: Issue #8767: please, give me access to https://github.com/fedora-infra or https://github.com/fedora-infra/fedmsg - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8767 18:02:34 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#8765 https://pagure.io/fedora-infrastructure/issue/8765 18:02:45 +1 18:02:50 so... I don't care if clime wants to take over fedmsg upstream, but I worry a bunch of development on it would cause people to not move away from it when we want them to 18:03:10 I want him to move it out of fedora-infra in that case 18:03:21 yeah, but we are actually still using it now. 18:03:30 no I mean his work 18:03:42 fork the project and do it in his own space 18:04:02 doing it in our space means that it looks like we are still working on it and we will be on the hook to fix things 18:04:11 yeah, that seems best. I don't know if he plans to fix/re-add/work on the packages too tho 18:04:55 how about we suggest he works in a fork for now,, after we are done we can give him the project entirely if he wants it? 18:04:56 nirik: i would like to yes 18:05:03 and +1 to move from fedora-infra once it is retired 18:05:09 hey clime 18:05:10 pagure.issue.comment.added -- smooge commented on ticket fedora-infrastructure#8767: "please, give me access to https://github.com/fedora-infra or https://github.com/fedora-infra/fedmsg" https://pagure.io/fedora-infrastructure/issue/8767#comment-636095 18:05:18 nirik: hello 18:05:32 clime: I am worried also if packages update and we have to do work on keeping it working for us... 18:05:38 basically, my current goal is not to let die fedmsg immediately 18:05:45 so, if you do update packages, please be carefull about backward compat 18:05:57 if i can do anything on top of that, that would be great! 18:06:14 nirik: ok 18:06:15 ok, so would a fork for now work then? 18:06:19 sure 18:06:28 cool. thanks! 18:06:38 .ticket 8768 18:06:40 nirik: Issue #8768: perl-sig should watch all perl packages - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8768 18:06:50 i think i don't need to update anything in epel7 18:06:51 nirik, close the fedmsg ticket? 18:07:11 smooge: yeah, I think for now... with the plan of giving the project after we are done with it. 18:07:20 so if you centos7, i shouldn't be able to break anything for you 18:07:24 pagure.issue.edit -- smooge edited the close_status and status fields of ticket fedora-infrastructure#8767 https://pagure.io/fedora-infrastructure/issue/8767 18:07:25 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8767 https://pagure.io/fedora-infrastructure/issue/8767 18:07:29 *you use 18:07:38 clime: we may have some fedora boxes too... not sure. 18:07:49 ah, ye ok, good to know 18:08:07 so, on this perl-sig one I guess we have a watchers endpoint so we just need to list all the perll* packages and run some script? 18:08:32 clime: I can try and look in more detail later. 18:08:54 I have 0 idea on this 18:08:59 so I guess move this one to waiting on asignee? does someone want to take it on? ;) 18:09:27 nirik: if you could, it would be cool 18:09:29 :) 18:09:30 https://pagure.io/pagure/c/f778bdc 18:09:33 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8768: medium-gain and medium-trouble https://pagure.io/fedora-infrastructure/issue/8768 18:09:34 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8768 https://pagure.io/fedora-infrastructure/issue/8768 18:09:45 nirik, done 18:10:00 .ticket 8770 18:10:01 nirik: Issue #8770: Change target release in bodhi update - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8770 18:10:11 clime, why not just use pyzmq? 18:10:11 cverna: you on this one? 18:10:34 Yes I ll assign it to myself 18:10:40 jcline / clime: can you discuss in #fedora-noc for now? 18:10:43 jcline: sry, pyzmq for what purpose? 18:10:43 pagure.issue.assigned.added -- cverna assigned ticket fedora-infrastructure#8770 to cverna https://pagure.io/fedora-infrastructure/issue/8770 18:11:03 .ticket 8771 18:11:04 nirik: Issue #8771: Fedorahosted git repo recovery: FortuneEngine.git - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8771 18:11:20 this just needs pulling from backups. I cna do it at some point... move to waiting on asignee 18:11:30 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8770: bodhi https://pagure.io/fedora-infrastructure/issue/8770 18:11:31 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8770 https://pagure.io/fedora-infrastructure/issue/8770 18:11:34 .ticket 8772 18:11:35 nirik: Issue #8772: install kernel03 - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/8772 18:11:46 just needs doing. I think smooge wanted to finish this one? 18:11:57 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8771 https://pagure.io/fedora-infrastructure/issue/8771 18:12:19 ok, thats infra needs review. Lets look at the releng ones that came in in the last few days. ;) 18:12:30 pagure.issue.tag.added -- smooge tagged ticket fedora-infrastructure#8772: hardware https://pagure.io/fedora-infrastructure/issue/8772 18:12:31 pagure.issue.assigned.added -- smooge assigned ticket fedora-infrastructure#8772 to smooge https://pagure.io/fedora-infrastructure/issue/8772 18:12:32 pagure.issue.edit -- smooge edited the priority fields of ticket fedora-infrastructure#8772 https://pagure.io/fedora-infrastructure/issue/8772 18:12:37 .releng 9332 18:12:38 nirik: Issue #9332: aarch64 Workstation bits need to be moved to primary mirrors - releng - Pagure.io - https://pagure.io/releng/issue/9332 18:12:45 nirik, yeah I didn't set it to anything until the meeting 18:13:15 so on this one, sounds like we just want to move aarch64, but leave armv7? 18:13:46 mboddu: I guess this needs partial copy changes and new-updates-sync changes? 18:13:58 nirik: Yes 18:14:23 I can work on it 18:14:44 I'm trying to think if we need any other acks... fesco? we should probibly notify mirror-admins list about it before we move... 18:14:49 Now that we know only aarch64 workstation should be promoted not others 18:15:04 and websites 18:15:41 ok 18:15:43 Right, I am not sure about the acks, but I can planning on sending the email to mirror-admins@ and creating the ticket with websites 18:15:55 s/can/am/ 18:16:06 .releng 9334 18:16:08 nirik: Issue #9334: Create place for ELN compose configuration files. - releng - Pagure.io - https://pagure.io/releng/issue/9334 18:16:13 mboddu: +1 18:16:21 This is I wanted to talk to you guys 18:16:25 so this is just a matter of making branches, etc... ? 18:16:33 I am okay with it 18:16:42 might hold off until the change is approved by fesco I guess, but otherwise it seems fine to me 18:17:06 Yes and giving access to jkaluza for the repos 18:17:11 although... that makes me wonder... 18:17:13 Since we cant do branch level acls 18:17:37 modular-defaults... they want to build modules against this also? 18:18:03 anyhow, it seems fine, but lets wait for fesco to approve the change. 18:18:17 .releng 9336 18:18:18 nirik: Issue #9336: Exception for epel8 branch for rpms/asio - releng - Pagure.io - https://pagure.io/releng/issue/9336 18:18:20 I think so 18:18:37 This is another ticket that I wanted to discuss 18:18:41 so, can we do this one with just --force on fedscmadmin? or do we need a solution to the json stuff? 18:18:53 We can do it with --force 18:19:18 But do we have a rule set modules? 18:19:21 https://pagure.io/epel/issue/100 18:19:28 in EPEL? 18:19:29 epel folks just approved this ^ 18:19:52 Haha, thanks nirik 18:20:02 so its allowed. But if we have a bunch of them, we should reconsider this --force thing. ;) 18:20:19 .releng 9344 18:20:20 nirik: Issue #9344: Automation for new branch creation does not consider group membership - releng - Pagure.io - https://pagure.io/releng/issue/9344 18:20:32 this I guess should be a fedscmadmin ticket? 18:20:46 have it expand groups? I don't know how hard that would be 18:21:01 yeah 18:21:30 we can close and reopen in fedscadmin 18:21:48 I dont know either but I did the previous work making only maintainers can request the branch, so I am gonna look into it 18:21:53 +1 if someone can do that. 18:21:56 cool. 18:22:03 Depends how pagure's api give that info, that might be trivial 18:22:03 ok, thats all the newest ones. 18:22:30 #info kevin closed 16 releng tickets friday, please do look and see if I missed anything in closing them 18:22:32 cverna: I have no idea, will know soon :) 18:22:45 but they were all things we already did or patches that were merged, etc. 18:22:45 Thanks nirik for grooming the releng tickets 18:23:15 I also have some PR's if folks have time... 18:23:24 https://pagure.io/infra-docs/pull-request/179 18:23:29 yeah 18:23:31 https://pagure.io/infra-docs/pull-request/177 18:23:37 https://pagure.io/infra-docs/pull-request/173 18:23:59 and https://src.fedoraproject.org/rpms/fedora-repos/pull-request/55 and https://src.fedoraproject.org/rpms/fedora-repos/pull-request/55 18:24:40 nirik, I have to go to another meeting 18:24:41 * mboddu looking at fedora-repos 18:24:43 pagure.pull-request.comment.added -- cverna commented on PR #179 on infra-docs https://pagure.io/infra-docs/pull-request/179#comment-113562 18:24:54 smooge: thanks. 18:25:03 * nirik looks to see if he also has to go to one he forgot 18:25:48 BTW, pro tip: https://src.fedoraproject.org/user//requests and same at pagure.io are nice to look at what needs merging. 18:26:04 thats all I had. Any other ones folks want to talk about ? 18:27:37 ok then... thanks everyone! 18:27:41 #endmeeting