18:00:45 #startmeeting EPEL (2019-07-17) 18:00:45 Meeting started Wed Jul 17 18:00:45 2019 UTC. 18:00:45 This meeting is logged and archived in a public location. 18:00:45 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:45 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:45 The meeting name has been set to 'epel_(2019-07-17)' 18:00:45 #meetingname epel 18:00:45 #topic Chair and Introductions 18:00:45 #chair bstinson Evolution nirik smooge pgreco tdawson 18:00:45 The meeting name has been set to 'epel' 18:00:45 Current chairs: Evolution bstinson nirik pgreco smooge tdawson 18:01:01 * mboddu is here 18:01:16 #topic Agenda 18:01:16 #info EPEL-8 Status 18:01:16 #info EPEL-8 Playground 18:01:21 hello everybody 18:01:27 #info this is a short meeting as I have a hard stop at 14:25 18:01:31 local 18:01:50 #topic EPEL-8 Status 18:02:13 The current status of EPEL-8 is needing some changes to fedpkg and fedscm-admin (which i am not sure what that is) 18:02:23 morning 18:03:06 hello nirik and mboddu 18:03:23 I want to thank both of you on getting the various changes into fedpkg and fedscm-admin done 18:03:44 smooge: Both of them are merged and I just built fedscm-admin but waiting for fedpkg folks to build fedpkg 18:03:56 once they get commited, pushed, and built for rawhide we can start working on epel8 branches 18:04:51 mboddu, where does fedscm-admin sit in things? I really have only seen it mentioned here and there 18:05:17 i am guessing it administrates certain controls to other apps? 18:06:52 well, we can use a locally patched fedpkg to build our base things out now right? 18:08:40 i believe so 18:09:13 if we can do that, i can work on getting things into the system this afternoon and evening 18:09:28 smooge: sit in things as in status now or in general where it is used? 18:10:09 mboddu, as in what does it do, where is it tied into the infrastructure. It is actually an out of meeting question I realize though 18:10:48 nirik, mboddu if we built an .infra patched version of fedpkg could it be installed in places and used? 18:11:35 smooge: .infra wont work as it should be shipped to everyone 18:11:42 hum, no, as I don't think it's in the base buildroots... 18:11:56 but do we need the modified fedpkg for builds or just on the client side? 18:12:01 smooge: fedscm-admin is the one that processes the ticket when someone requests a ticket 18:12:08 also, did we fix/look at fedpkg-minimal? 18:12:13 Sorry, requests a branch or repo in dist-git 18:12:22 nirik: Nope :( 18:13:10 mboddu, at the moment it needs to be shipped to 3 people and a couple of systems. The version which would be built by them would replace that on everyone's system 18:13:15 thats actually whats used in the srpm builds 18:13:37 ok so I need to look at fedpkg-minimal after this meeting and see what needs to be done there 18:13:49 it should hopefully be little to nothing. 18:14:01 it's basically a sh script that only does 'fedpkg sources' 18:14:12 nirik: Yeah, we need to look at that 18:14:52 smooge: I guess we can build a fxx.1 version of fedpkg and send it to those 3 people to test it 18:16:32 smooge, nirik : https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?h=master&id=752ba3de32532fea0a56e8824afc8252b83c3549 18:16:53 ^ should add the pdc entries and also will add packages to koji tags 18:17:01 mboddu, the 3 would be you me and nirik 18:17:03 * nirik nods. 18:17:32 I can also do that after the next meeting 18:17:40 smooge: Oh, then I guess we can do a scratch build in that case 18:17:46 or you could that 18:18:30 mboddu, sure. I think we are the only people who will need it for 24-48 hours until we can get things built enough that other people can even want to look at things 18:18:32 smooge: Sure, nirik and I are on rawhide, I can build one for rawhide 18:18:40 it would be troy but we will have to make up for him 18:19:07 .. realizes he will need to set up a rawhide box 18:19:42 nirik: While I think about it, we need to fix koji-sync-listener.py I guess 18:19:44 * mboddu looks 18:20:38 ok anything else for this meeting people want to bring up? 18:20:43 #topic Open Floor 18:22:12 nirik: Quick question 18:22:58 If epel8 has a package foo, epel8-playground which is inheriting from epel8, while trying to add the package to epel8-playground, does it affect in anyway? 18:24:08 not sure there. 18:24:22 we can look and see and adjust 18:24:41 nirik: Okay, but I need to add epel8-playground to the list as well 18:24:58 Since we definitely need to add pdc entries for it 18:25:17 ok 18:25:41 perhaps now I am thinking it shouldn't inherit from epel8... 18:25:57 since when people do builds it will automatically build for both epel8 and epel8-playground 18:26:04 dunno, we can adjust 18:26:12 * nirik has to go to another meeting soon here. 18:27:21 What would be the problem with it? 18:27:30 Anyway, as you said, we can adjust 18:28:03 well, I just don't know if it's needed. 18:28:20 ok I have to end this and go to naother meeting. Sorry 18:28:32 nirik: Okay 18:28:35 me too 18:28:36 #endmeeting