18:00:27 <smooge> #startmeeting EPEL (2018-04-25)
18:00:27 <zodbot> Meeting started Wed Apr 25 18:00:27 2018 UTC.  The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:27 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:27 <zodbot> The meeting name has been set to 'epel_(2018-04-25)'
18:00:27 <smooge> #meetingname EPEL
18:00:27 <zodbot> The meeting name has been set to 'epel'
18:00:28 <smooge> #topic aloha
18:00:28 <smooge> #chair avij bstinson Evolution nirik smooge
18:00:28 <zodbot> Current chairs: Evolution avij bstinson nirik smooge
18:00:47 <nirik> present (mostly)
18:01:21 <avij> hello
18:01:42 <smooge> ok will see if we can get bstinson and we have quorum
18:01:50 * bstinson is here
18:02:06 <smooge> #topic agenda
18:02:06 <smooge> #info 7.5 release
18:02:06 <smooge> #info flock talks
18:02:06 <smooge> #info open floor
18:02:19 <smooge> #topic 7.5
18:02:37 <smooge> #info EL7.5 came out a bit ago. We have updated the builders the day it came out
18:02:59 <smooge> #info some people have reported problems with desktop builds on older OS
18:03:31 <smooge> avij, bstinson how are things in "what the hell people?" land?
18:03:41 <nirik> we should likely find a list of added to rhel packages and block/retire them
18:03:48 <smooge> yep.
18:04:12 <bstinson> We expect CentOS CR (https://wiki.centos.org/AdditionalResources/Repositories/CR) to come out ReallySoonNow(TM)
18:04:47 <smooge> so we have moved from "WhenItsDone" to " ReallySoonNow(TM) "
18:04:53 <smooge> always good to see that
18:04:59 <avij> indeed. there's progress.
18:05:19 <smooge> anything EPEL related you might need to get dealt with?
18:06:10 <bstinson> one nice feature of this point-release: The alternate architectures were all built together, so this will make dealing with package work in EPEL a little easier to track
18:06:20 <smooge> ah good
18:06:26 <avij> I'm sorry I'm lagging a bit behind in all this, mostly due to my 10-day trip that started right when RHEL 7.5 got released
18:07:00 <smooge> understood. most of us have been on similar delays
18:07:38 <avij> the only somewhat EPEL related issue I've already run into was libsmbios, but that's really an issue that needs to be dealt with by RH/Dell. https://bugzilla.redhat.com/show_bug.cgi?id=1570019
18:08:05 <avij> retiring libsmbios from EPEL will not help, but obviously it'd need to be done at some point anyway
18:08:36 <avij> tl;dr is that EPEL's libsmbios works in this case, RH's doesn't.
18:09:21 <smooge> ha
18:09:24 <smooge> ok
18:09:35 <smooge> #topic flock talks
18:09:50 <smooge> OK Flock is coming up this summer in Dresden Germany
18:10:10 <smooge> I would like for various EPEL related talks to be done
18:10:32 <smooge> so figured it would be a good idea to bring it up now so we can all go "hmm no idea" now versus at deadline time
18:11:14 <Evolution> is the cfp open for flock?
18:11:14 <smooge> I will have this on the agenda for a while for spitball ideas
18:11:40 <smooge> not that I know of, but we might as well start now.. and then we can also look at being ready for other things
18:11:48 <nirik> I can think of a number of talks... but not sure I would be the one to give them. ;)
18:12:36 <smooge> well we will spitball them for next week and find someone to give them
18:13:20 <smooge> OK I am oncall and dealing with some offcomputer things so my brain is toast. I only have open floor after this
18:13:58 <smooge> #info FLOCK CFP will be soon. Next week we will spitball topics to discuss there
18:14:02 <smooge> #topic Open Floor
18:14:31 <smooge> ok anyone have anything from the open floor? I am thinking there are several things.. but I am needing another cup of coffee and some tums for the coffee
18:15:06 <nirik> I'm curious if there are plans for the python34 to python36 switch, but I can ask that on the list.
18:15:25 <nb> i kinda do
18:15:40 <nb> it'd be nice if we could make some exceptions to the "don't provide packages that RHEL provides"
18:15:48 <nb> RHEL has kinda abandoned some golang packages
18:16:00 <nb> which makes it hard/impossible to build some other packages since they wont' update their pacakges
18:16:17 * carlwgeorge 's ears perk up
18:16:27 <nb> although the deps are only needed while the other packages are being built, since golang static links everything
18:16:43 <bstinson> nb: do you have a specific example in mind?
18:16:44 * nb was looking at packaging rclone in EPEL7 but i run into dephell
18:16:52 <nb> bstinson, /me looks, just a sec
18:17:22 <nb> googlecode-golang-net is one i believe
18:17:25 <nb> and i think -crypto also
18:17:28 <nb> and /me looks for more
18:18:13 <nb> bstinson, https://bugzilla.redhat.com/show_bug.cgi?id=1409553
18:18:14 <nirik> well, how do we decide if something is "abandoned"
18:18:19 <carlwgeorge> #info https://bugzilla.redhat.com/show_bug.cgi?id=1409553
18:18:42 <nb> nirik, well, FWIW they never have to be pushed to the repos
18:18:56 <nb> nirik, all that really needs to be done is branch the packages for epel and then add a BR override
18:18:57 <smooge> well they do because of how the build system works
18:19:26 <nirik> oh I see what you are saying... just BR only
18:19:41 <smooge> and I should have waited until then
18:19:49 <carlwgeorge> there are also packages that have already been published but are uninstallable due to these issues, such as golang-github-aws-aws-sdk-go-devel https://bugzilla.redhat.com/show_bug.cgi?id=1568131
18:19:53 <smooge> my problem with that is that how does a person make that package again?
18:19:55 <nirik> and specific to go since it's static
18:20:27 <smooge> we have basically created un-rebuildable packages
18:20:42 <nirik> nb: would you be willing to write up a proposal and send to the list? I don't think we want to decide that ad-hoc without some thought/input.
18:21:02 <nb> from what i understand, RHEL has stopped shipping/updating those packages and just bundles everything now
18:21:03 <nirik> smooge: yeah, you would need all the same buildroot overrides
18:21:12 <nb> nirik, I will try to remember to do so
18:21:23 <smooge> I agree with nirik on that. I am probably not understanding something so a proposal would be better
18:23:26 <smooge> ok thanks nb
18:23:40 <smooge> alright anything else?
18:23:57 <avij> not at the moment
18:24:05 <smooge> ending meeting in 30 otherwise?
18:24:31 <smooge> #endmeeting