18:03:48 #startmeeting EPEL (2019-07-10) 18:03:48 Meeting started Wed Jul 10 18:03:48 2019 UTC. 18:03:48 This meeting is logged and archived in a public location. 18:03:48 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:03:48 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:03:48 The meeting name has been set to 'epel_(2019-07-10)' 18:03:48 #meetingname epel 18:03:48 #topic Chair and Introductions 18:03:48 #chair bstinson Evolution nirik smooge pgreco tdawson 18:03:48 The meeting name has been set to 'epel' 18:03:48 Current chairs: Evolution bstinson nirik pgreco smooge tdawson 18:04:05 morning 18:04:08 Evolution sends his regards 18:04:23 tdawson is on a 200 hour plane flight 18:04:32 * bstinson is here 18:05:00 ok so I think we are just going to announce some stuff and go on 18:05:08 hi bstinson 18:05:43 next week Evolution, tdawson, and bstinson will not be around so I think a cancel will be on order 18:05:57 ok 18:06:19 so topics 18:06:27 #topic EPEL-8 Status 18:07:04 so mboddu put in various items for EPEL-8 into koji yesterday 18:07:19 * mboddu is here now 18:07:43 we ran into a problem however in that fedpkg has a filter which stops epel8-playground or epel-playground8 branches 18:07:44 smooge: Once we have the blocker from fedpkg fixed, we are ready 18:08:26 mboddu, is what I wrote above the blocker or is there anything else? 18:08:46 I wonder if we can just bypass that for the initial things we need to build, but we can sort that out out of meeting. 18:09:29 smooge: Nope, I started working on the pungi configs for epel composes, but thats not right now afaik, right? 18:09:53 * pgreco arrives late and reads back 18:10:34 ok I am going to switch to the next topic as it is related 18:10:42 #topic EPEL-8 Playground 18:11:13 So the epel-rawhide has a final name epel-playground 18:12:08 I hope it will be useful for folks... 18:12:39 the part which needs a bikeshed is whether it should be epelN-playground or epel-playgroundN 18:13:02 I think the first looks more 'normal', but I don't care too much 18:13:05 "Lets play EPEL in the playground" :D 18:13:24 I like epel8-playground better 18:13:32 just because it uses epel8 as prefix 18:13:40 the same as the real branch 18:13:49 * mboddu made the patches assuming epel8-playground 18:13:49 +/-0 but would default to epelN-playground 18:13:59 ok .. I will rework the patch after the meeting 18:14:08 but not set in stone about it ;) 18:14:20 mboddu, did you completely replace my patch? I just saw a couple of line differences 18:14:28 smooge: Lets wait and see, if my patch works then you dont have to do anything 18:15:01 ok. I saw a bunch of other lines assuming a certain pattern I was changing 18:15:22 in any case.. all hail epel\d+-playground 18:16:05 smooge: Both of our patches are different, I guess your patch requires to have a epel-playground as a release in pdc, where as mine uses the existing epel release 18:16:06 this is meant for the times for getting EL8.Y out the door 18:16:18 so will epel8-playground have a different dist tag? I can't recall if we discussed that yet. 18:16:37 smooge: Thats why I want the input from them 18:16:49 nirik: We haven't discussed that 18:17:01 nirik, I assumed it didn't.. there are parts in the code which does that 18:17:35 but remembering the various repotag wars.. we might want one 18:17:37 I could go either way... .epel8 is easy, but it might be nice to see easily you installed from playground so .epel8.playground might be nice. 18:17:50 nirik: If its a different dist-tag, then I think I need to change the design and separate epel8-playground from epel tags in koji 18:18:29 * smooge probably should have all this written down in a planning document 18:18:34 mboddu: well, it should just be a change in epel-release no? but if it needs more work it might not be worth it. 18:19:15 nirik: Now I think about it, why should we inherit epel8-playground to epel8 tag? Should we keep them separate? 18:19:47 inherit epel8-playground from epel8 tag?* 18:20:01 I think that might be best... 18:20:25 if we are setting config so 'fedpkg build' builds for both by default... they don't even need to inherit builds... 18:20:40 nirik: Yeah, which is what I am thinking now 18:20:47 so looking in the code there is a place where it asks pdc with short_name = product_version['short'] 18:20:51 They have their own buildroots anyway 18:21:58 smooge: Yes, which is why I said your patch might require adding epel-playground as a release to pdc and it might only work with 'epel-playground8' 18:22:10 ah ok 18:22:31 I fear we are going to get people who change config to use playground, then forget to put it back and stop building for both, but I guess we can cross that bridge when we come to it. 18:23:06 mboddu, ok I think we need to get some info from them then. 18:23:17 blankety-blank-blank 18:23:36 wanted to get some packages built 18:24:05 smooge: Exactly, I dont want to assume something and they come back to us and say "You did everything wrong" 18:24:33 ok what if we put in the playground stuff later? 18:25:06 smooge: That means, who ever requested epel8 branches have to request epel8-playground separately 18:25:45 * smooge was thinking of if we did this for EPEL7 we would need that later anyway. 18:26:17 ok no easy answers 18:27:04 and we will be behind a bunch of builds 18:27:10 which we will have to do again 18:28:31 yeah.. ok so wait 18:28:40 I will put it in as a blocker for management 18:29:12 alright then 18:29:18 I think the fedmsg maintainer is in china... so might be he chimes in late today 18:29:36 #info EPEL-7.7 preparedness? 18:29:38 ^fedmsg=fedpkg 18:29:43 :) 18:29:52 #topic EPEL-7.7 preparedness? 18:30:17 7.7 is coming up sometime soon.. I expect it is just a matter of time 18:30:35 mboddu: yeah, sorry. 18:30:43 I think we will have to muddle through it like past dot releases versus using branching tools or anything 18:31:55 #topic Open Floor 18:32:03 anything for open floor today? 18:33:34 ok in that case.. thank you all for coming this week. Hopefully we will be moving forward next week. 18:33:37 #endmeeting