18:01:03 #startmeeting EPEL (2017-08-09) 18:01:03 Meeting started Wed Aug 9 18:01:03 2017 UTC. The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:03 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:01:03 The meeting name has been set to 'epel_(2017-08-09)' 18:01:03 #meetingname EPEL 18:01:03 The meeting name has been set to 'epel' 18:01:03 #topic aloha 18:01:03 #chair avij bstinson Evolution nirik smooge 18:01:03 Current chairs: Evolution avij bstinson nirik smooge 18:01:32 Hi. I am not sure if we are going ot have quorum again this week. avij is on travel and I have not heard from Evolution 18:02:02 If we get bstinson we will have minimum and can run through the motion 18:02:06 and nirik 18:02:07 morning 18:02:13 morning. 18:02:17 morning 18:02:23 oh my its an Evolution 18:02:28 hi all 18:02:29 I finally made it 18:02:31 yay 18:03:16 hi bstinson and we have quorum 18:03:26 #topic Announcements 18:03:26 #info RHEL-7.4 released 18:03:26 #info FLOCK 2017 in 3 weeks 18:03:33 well Flock is in 2 weeks 18:03:43 I didn't update that line 18:03:55 Currently the EPEL meetings are on Wednesday. 18:04:14 I have worked out an outline for the state of the union which I will mail out later today 18:04:24 and get items people want to go over 18:04:41 and then I will put in the Activity day items for the work afterwords 18:05:16 one of the meetings is going to be against spot's "why i drink" so I expect our attendence might be light then 18:05:24 or drunk 18:06:02 :) 18:06:07 Evolution, bstinson on the EL-7.4.. I saw there were a bunch of package problems. Anything we in EPEL can help with? 18:07:10 has anyone looked through the packagesets yet? 18:07:17 * spot makes a note to bring drinks to that talk 18:07:40 bstinson, I am not sure what you mean? As in duplicates? 18:07:44 smooge: from an epel side, I don't think so. There are some build deps that clearly come from epel, but aren't always the current version 18:07:51 so the repo itself wouldn't necessarily help 18:08:17 smooge: yeah. additions, subtractions to base that would affect EPEL 18:08:19 but once the proper versions get pulled into CentOS we will need to look at 'fixing' it somehow 18:08:33 we have about 5 packages which need to be dealt with. 18:08:39 smooge: I don't think they're required to *run*, just to build. 18:09:07 so they may not be shipped with the distro. they may get put into plus or something 18:10:10 #topic ansible in rhel-7-extras https://pagure.io/epel/issue/40 18:10:20 speaking of packages in epel and rhel 18:10:47 nirik, did you have anything on this? 18:10:56 yeah... 18:11:02 so, ansible is now in rhel7 extras 18:11:12 but... it's 'unsupported' 18:11:39 the epel one will get removed in a few weeks (they asked me to hold off removing it for a bit until they had everything lined up) 18:12:04 so probibly I need to do a blog post and epel announce, etc... I am not sure how fast they will be updating. 18:12:32 does it require rolling versions backward? 18:12:41 I haven't looked to see which one they actually shipped 18:12:44 https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/7.4_Release_Notes/index.html#technology_previews_red_hat_enterprise_linux_system_roles_powered_by_ansible 18:12:53 dunno if epel was newer than rhel-extras 18:13:30 they were supposed to make their one newer... but I didn't check. 18:13:32 * nirik does so 18:13:59 ansible-2.3.1.0-3.el7.noarch.rpm 18:14:16 epel has: ansible-2.3.1.0-1.el7.noarch 18:14:20 so it should upgrade fine 18:15:00 other packages I knew about having conflicts 18:15:03 http-parser intel-cmt-cat libgpod nftables po4a 18:15:36 there may be a couple others as we were going off of a partial list of repos 18:16:08 Evolution, what does CentOS do with the RHEL-extras? Is that in CentOS-extras, the main repo or something else? 18:16:19 smooge: centos-extras 18:16:23 which is enabled by default 18:17:00 ok I will try to get a full list of packages out to the list later today 18:17:28 nirik, for getting them out of epel and blocked.. we should use a releng ticket or something else? 18:17:40 well, there's a bug on it already... 18:17:51 but in general yeah. 18:18:17 ok I didn't know there was a bug already 18:19:57 well, on the ansible thing... not others; 18:20:05 Ah ok I will do the others 18:20:26 Evolution, the build-requires that you are needing were you able to get them out of koji? 18:21:56 #topic Ticket https://pagure.io/epel/issue/39 18:22:13 OK this is a similar removal of a package from EPEL 18:22:33 * nirik thinks that is a reasonable plan. 18:23:02 cool. Evolution bstinson anything for this ticket? 18:23:03 smooge: yeah. we got them out of koji just fine 18:23:14 sorry. crappy wifi in hotel 18:23:29 no 18:23:30 prob 18:23:31 le 18:23:32 m 18:23:37 heh. 18:23:46 nah, I'm fine with nuking ceph from epel. 18:24:06 +1 from me 18:24:18 +1 from me 18:24:42 #agreed Remove ceph from EPEL with plan in ticket 39 18:25:19 #topic Ticket https://pagure.io/epel/issue/7 18:25:27 I wanted to clean up some old tickets also 18:26:16 this was uhm old old 18:26:17 didn't that get done? 18:26:21 or never did? 18:26:40 I don't think it automatically does 18:26:55 I believe till was waiting for us to say yay on it 18:27:06 at this point I am good for yay 18:27:23 \o/ 18:27:25 yay 18:27:57 nirik, bstinson you ok on going ahead if it isn't already? 18:28:08 sure. 18:28:36 +1 18:29:48 ok cool. 18:31:00 #agreed Go with auto-retirement if it isn't already there 18:31:10 #topic Ticket https://pagure.io/epel/issue/4 18:31:15 last ticket for this week 18:31:46 I will be putting together a policy and putting it in the ticket later this week 18:31:55 so nothing to decide as we did that already 18:32:01 just wanted to give a status 18:32:07 and speaking of documentation... 18:32:17 #topic Document https://pagure.io/epel/blob/master/f/docs/source/EPEL-meeting-process.rst 18:32:45 I am going through our old wiki pages and putting them as rst in here 18:33:18 I would like to figure out how to get this to pretty document like releng and fesco pagure do 18:33:28 any help or ideas would be welcome 18:33:59 This week I will be doing the About_EPEL and Joining_EPEL documents and hopefully get the wiki ones ready to retire 18:34:31 Anyone who has time/energy/need to proofread are welcome to help me here 18:34:50 that pretty much leads to the last 2 items on the agenda 18:35:18 unless anyone has something on documents (or documents that should be moved over /updated as soon as possible? 18:36:37 #topic Next Meeting Agenda 18:37:35 ok my plan for the next couple of meetings is to try and get some old tickets dealt with, a review of any documents/policies that need to be dealt with, etc 18:38:02 however my first question is who is available next week? and who is going to be at FLOCK? 18:38:14 Evolution, bstinson nirik ? 18:38:28 * nirik got sidetracked. sorry. reading 18:38:36 * bstinson will be at both 18:38:48 I should be here next week and should be also at flock to heckle^Whelp 18:40:01 I expect Evolutions wifi has him reading an empty page 18:40:11 bstinson, thanks. I look forward to seeing you again 18:41:12 I don't think avij will be going to FLOCK so the meeting in 2 weeks may just be us 3 in person (unless Evolution is going to be there) Is that ok with everyone? 18:42:07 i believe Evolution was planning on heading there 18:42:21 (not speaking for him of course :) 18:43:52 understood 18:44:14 ok I think that is it for this topic. I look forward to seeing who can make next week and everyone who is at Flock 18:44:19 #topic Open Floor 18:44:37 I will close the meeting in 2 minutes if there are no open floor items 18:45:54 Thank you all for coming this week. 18:46:56 #endmeeting