18:00:34 #startmeeting EPEL (2019-04-03) 18:00:34 Meeting started Wed Apr 3 18:00:34 2019 UTC. 18:00:34 This meeting is logged and archived in a public location. 18:00:34 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:34 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:34 The meeting name has been set to 'epel_(2019-04-03)' 18:00:34 #meetingname epel 18:00:34 #topic Chair and Introductions 18:00:34 The meeting name has been set to 'epel' 18:00:34 #chair bstinson Evolution nirik smooge pgreco tdawson 18:00:34 Current chairs: Evolution bstinson nirik pgreco smooge tdawson 18:00:45 morning 18:00:54 afternoon ;) 18:00:57 hello 18:01:14 * bstinson waves 18:01:52 Hello 18:03:13 #topic Agenda 18:03:14 #info Python36 pushed to stable 18:03:14 #info https://pagure.io/epel/issue/53 18:03:14 #info https://pagure.io/epel/issue/33 18:03:21 Evolution is out this week 18:03:44 #topic Python36 Pushed to stable 18:03:44 #info Many thanks to all who helped 18:03:44 #info time to push more to python3 to epel7? 18:04:11 tdawson, do you have anything which you wanted to add? 18:04:25 Just want to thank everyone who helped. 18:04:45 well it looks like epel7 pushes failed last night 18:04:55 tdawson, amazing job!!! 18:05:04 yeah, they did. ;) but we will get it fixed... 18:05:08 There were several people who did testing, found and fixed problems. 18:05:26 i did various testing on things but wish we had more people helping 18:06:05 I suspect there will be some people surprised, etc... but thats ok, we will just do the best we can to help them 18:06:20 yep 18:06:33 you get what you put into it 18:06:45 the plan has been in the works for several months 18:07:03 and it was publicly advertised, so... 18:07:11 I just want to say that the people who worked on it did a great job 18:07:25 +1 yeah, many thanks. 18:07:39 anything else on this from people? 18:08:06 will the updates be pushed tonight? 18:08:26 as soon as we sort out what went wrong. 18:08:26 Nothing from me 18:08:39 #topic https://pagure.io/epel/issue/53 18:10:08 So it looks like a package which has no longer upstream support with a different version having said support 18:10:47 I think the general policy of 'announce, put in epel-testing for 4 weeks or +3 karma and then go' 18:11:13 should cover it... and want feedback from the rest of the committee 18:11:27 yeah, in the new world of minor releases (whenever we get to that) we would just tell them to wait for 7.7 or whatever? 18:12:43 smooge: I second what you said "announce, put in epel-testing for 4 weeks or +3 karma and then go" 18:12:52 in the new world, looks like they want to bump the el6 package too...which would be the usual process for that release 18:13:13 yeap, I'm a little worried about el6 18:13:48 but really don't know the package to have a clear idea 18:13:50 +1 18:14:15 +1 for announce/epel-testing/wait from me 18:14:23 bstinson, nirik, yes for new world it would be wait for EL-7.7 and for EL-6 it would be bump and release 18:14:51 I don't know if we will have the items in place for EL-7.7 so am not sure we could say that currently 18:15:03 cool. No objections to just announce/testing now, just wanted to clarify the process after we have minor releases. 18:15:08 sure 18:15:26 ok I will agree and note in the ticket that in the future we would have them wait until 7.7 18:16:47 #agreed "announce, put in epel-testing for 4 weeks or +3 karma and then go" (4 +1 , 1 abstain, 0 -1) 18:17:04 #topic https://pagure.io/epel/issue/33 18:17:17 Going through the old queue 18:18:02 that should be a bug in bugzilla for the maintainer 18:18:13 IMHO 18:20:43 So, that ticket is 2 years old, but it looks like monit was updated in EPEL7 about a year and a half ago 18:20:53 ok will close out 18:21:06 ok that is all I have for tickets this week 18:21:48 #topic open floor 18:22:02 The monit in epel7 is currently the same version as regular Fedora, for those that are wondering 18:22:49 I have something, wrt altarch 18:23:17 some people have been asking me about a signed version of the armhfp epel release 18:23:48 I know they can't be built inside the epel infrastructure, and that's ok 18:24:28 but I'd like to know if it is worth considering building those from within centos' infrastructure 18:24:48 so this was an idea I had about that.. nirik what if we signed the key that was used to sign the EPEL-7 arm using the key we use for EPEL-7? 18:25:31 then they build the packages in CentOS signing with their key 18:25:55 my idea is to apply the same to i686, fwiw 18:25:57 I'm not sure that would help any... 18:26:29 * nirik has no idea what centos infra has setup for this kind of thing. 18:26:44 nirik, there is none 18:26:57 all I've been doing is based on temporary infra 18:27:06 i'm personally sitting at -1 for signing with a Fedora/EPEL key. we *could* see about getting a CentOS SIG-like key 18:27:24 bstinson, I'm more inclined to that too 18:27:37 el8 is probably a good time to revisit 18:27:39 so I am not looking at signing with a Fedora/EPEL key... just signing the key in a trust measure 18:27:42 but definitely for el7 18:27:52 using a separate epel-release, or whatever we want to name it 18:28:08 pgreco: the problem here is the branding 18:28:10 because it would also point to different servers... 18:28:13 yeap 18:28:23 smooge: I bet the number of people who would look at that is... very very small. :) 18:28:26 it wouldn't be epel 18:28:32 nirik, agreed. 18:28:41 but it would answer the usual questions 18:28:57 or we could go with the other idea like EPIC 18:29:03 I signed the fedora keys for a while, then stopped and neither before nor after did anyone comment about it at all. 18:29:06 EPEL packages in CentOS 18:29:26 I think it should be it's own thing, yeah. 18:29:33 nirik, understood.. it was an idea that came to me at 4 am a couple of days ago 18:29:50 and I was going to see if it had any merit. and like most 4am ideas... 18:30:17 pgreco, I would be happy to be part of any CentOS SIG to help out on this 18:30:28 pgreco: that's still on those plague builders? 18:32:45 yeap, still on plague :( 18:33:34 works so far, but with el8 around the corner, and Arrfab wanting to remove those plague builders 18:33:39 it may be time 18:33:47 ah plague, I remember it well 18:33:48 smooge, any help I can get :D 18:34:02 i think we can probably come up with something 18:34:08 I was thinking of making plague3 18:34:21 with python36 18:34:43 bstinson, what architectures does CBS build for? 18:35:56 aarch64 ppc64{,le} i386 and x86_64 18:36:09 ah thus the problem with arm 18:36:12 we have armhfp builders, but i don't think we have any released content out of there yet 18:36:36 ok so I think that would be a different meeting in a different channel then? 18:36:37 smooge, those armhfp builders came back to life with your ssds 18:37:56 cool 18:38:30 well, all I wanted for today was to put it out there, so we could revisit at a later meeting 18:38:33 bstinson, pgreco would this be better covered next week on Mondays CBS/Infrastructure meeting or a different meeting time? 18:38:35 so we did way more 18:39:07 I'm ok with that 18:39:17 monday I mean, what time? 18:39:22 smooge, pgreco: we can definitely work out the keys at the CBS meeting. we'll need a sponsor (which i'm sure we can find) 18:39:34 the build process we should probably hold on for a little bit 18:39:51 14:00 UTC 18:39:53 on monday 18:40:09 #centos-devel until #centos-meeting is created 18:40:42 who can sponsor? Exxon-Mobile? 18:41:14 someone from the Core SIG takes on that role 18:42:03 ok cool 18:42:10 easier to get than Exxon 18:43:11 pgreco, anything else on this? 18:43:22 and any other items for today? 18:43:30 * nirik has nothing 18:43:36 not really, thanks! 18:43:49 Nothing from me 18:44:02 ok thank you very much 18:44:38 will see some of you next Monday in #centos-devel and next Wednesday in #fedora-meeting 18:44:46 #endmeeting