19:01:49 #startmeeting EPEL (2019-11-12) 19:01:49 Meeting started Wed Nov 13 19:01:49 2019 UTC. 19:01:49 This meeting is logged and archived in a public location. 19:01:49 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01:49 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:01:49 The meeting name has been set to 'epel_(2019-11-12)' 19:01:49 #meetingname epel 19:01:49 The meeting name has been set to 'epel' 19:01:49 #topic aloha 19:01:50 #chair nirik smooge tdawson bstinson Evolution pgreco sgallagh 19:01:50 #topic Intros 19:01:50 Current chairs: Evolution bstinson nirik pgreco sgallagh smooge tdawson 19:01:50 #info Meeting is run from https://board.net/p/epel 19:01:56 and I am still off 19:02:15 * tdawson is here 19:02:21 hello 19:02:57 #topic Old Business 19:03:07 @time 19:03:22 that isn't right at all 19:03:39 .date 19:03:39 smooge: 07:03 PM, November 13, 2019 19:03:51 Huh ... that's my time zone 19:03:53 ok so the meeting is generally at 1800 UTC 19:04:15 do we want it to be still at that time 19:04:28 whatever is easier for those with DST 19:04:35 I'm fine either way 19:04:48 It's just around my lunch time, so when I get it wrong, I tend to miss it. 19:05:53 understood. 19:06:08 ok I am going to keep it at 1800 UTC for the time being since we don't have quorum today 19:06:23 #topic EPEL-6 19:06:23 #info EPEL-6 is End of Life in 2020-11. It will be moved to archives in 2020-12 19:06:23 #topic EPEL-7 19:06:23 #info https://bugzilla.redhat.com/show_bug.cgi?id=1731420 19:06:24 #info https://pagure.io/epel/issue/94 19:07:19 so the bugzilla was brought up on the mailing list. I think that basically they should be able to move forward on this since there are problems with the existing version 19:08:23 the other items is the one I think tdawson wanted to talk about 19:08:45 Correct 19:09:16 I agree about the bugzilla though, I think they should move forward with it. 19:09:27 Or, I approve, whatever the correct term is. 19:10:29 is there any side effect of enabling it?, I'm not that familiar with it.... 19:10:44 As for the python generators being turned on by default (Issue #94), this has been turned on since F30 19:10:57 The side affect is that you might have double dependencies. 19:11:11 I haven't heard of that breaking anything though. 19:11:41 so the plan is to enable in 8, and if nothing breaks badly, do 7 too? 19:11:53 i do not have a problem with enabling python either 19:12:23 To me, that sounds like the right plan. Enable it in 8, give it a month or so, then if nobody screams, enable it in epel7 19:12:36 +1 19:12:37 yeap, +1 19:13:07 Is 3 enough for a passing vote? 19:13:53 I guess 3 is a quorum, so that would be a yes. 19:15:36 #topic EPEL-8 19:15:52 nothing to say here without merlinm or sgallagh 19:16:03 #topic Open Floor 19:16:25 oh wait... merlinm do you have anything to say? 19:16:33 Not sure what to add. 19:16:56 epel8 module builds were basically working in staging, but something broke again 19:16:57 I've been working with Merlin, or at least testing. I thought he had said things were pretty much ready and stable in stg. 19:17:15 something broke? 19:17:20 *sigh* ... ya ... like what he just said. :) 19:17:37 What broke wasn't with modules, it's general epel8 package building. 19:17:41 see #epel, package downloads started failing. 19:18:01 I've been working with mboddu to get composes working. 19:18:38 oh I didn't know that was a constant thing .. 19:19:43 * tdawson give is another try, just incase something changed. It fails pretty early. 19:21:08 it should be ./x86_64/RHEL-8-001/non_modular/audit-libs-3.0-0.13.20190507gitf58ec40.el8.x86_64.rpm 19:21:30 Of course ... there is the wait until you get a slot in the build queue ... so it might be a while. 19:22:38 so I don't know what thinks the .10 came from. did anyone try a regenrepo? 19:22:41 There we go ... https://kojipkgs.stg.fedoraproject.org//work/tasks/9128/90169128/root.log 19:24:05 I don' t know. I don't have permissions for that in fedora or fedora stg 19:24:23 Nor I. 19:25:39 ... sees if he does 19:26:53 well if I do.. it failed anyway. I think I will have to see if mboddu can try it 19:27:26 merlinm: So, if we get it working, and it looks like it's good in stg, what is the next step? 19:28:25 We still need to get composes working. Then plan for getting it all going in prod. 19:29:47 What do you mean when you say "composes" ? epel8 repo composes? 19:30:48 Yes. In staging first, of course. 19:31:39 Modular updates need to be sorted out, too. But I just don't know how much of that can be done in staging. 19:32:54 Modular updating is going from one stream to another, correct? 19:33:12 no, inclusion in Bodhi 19:33:14 (hi) 19:33:15 No. Bodhi updates. 19:33:21 Ohh ... ok 19:33:46 * mboddu reading back 19:34:10 ok has no idea what is pulling in the old audit in koji 19:35:52 Do I need to regen the repo? 19:36:20 so I did a koji regen-repo epel8-build 19:36:31 Also, the current blocker with epel8 modular composes is - https://pagure.io/releng/issue/8968#comment-610931 19:36:47 but that regen-repo doesn't affect external repo 19:36:56 i don't think 19:38:38 ok one topic at a time 19:40:15 * mboddu looking at the build failure 19:44:55 ok I think we don't have anything else for this meeting 19:45:00 thank you all for coming this week 19:45:08 will see you next week at 1800 UTC 19:45:08 thanks 19:45:13 #endmeeting