18:00:40 <smooge> #startmeeting EPEL (2018-09-19)
18:00:40 <zodbot> Meeting started Wed Sep 19 18:00:40 2018 UTC.
18:00:40 <zodbot> This meeting is logged and archived in a public location.
18:00:40 <zodbot> The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:40 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:40 <zodbot> The meeting name has been set to 'epel_(2018-09-19)'
18:00:40 <smooge> #meetingname epel
18:00:40 <zodbot> The meeting name has been set to 'epel'
18:00:41 <smooge> #topic Chair and Introductions
18:00:41 <smooge> #chair avij bstinson Evolution nirik smooge
18:00:41 <zodbot> Current chairs: Evolution avij bstinson nirik smooge
18:00:51 <nirik> morning everyone.
18:00:54 <smooge> Hello
18:00:59 <avij> evening
18:01:26 <smooge> so how are you all doing
18:01:59 <Evolution> o/
18:02:05 <smooge> Ok this meeting is pretty short.. our first topic is!
18:02:13 <smooge> #topic When should we meet from now on
18:02:17 <smooge> http://whenisgood.net/zgt7jmc/results/bebba9f
18:02:26 <smooge> thank you all for putting up times.
18:02:47 <smooge> those times are GMT
18:02:55 <smooge> or are on my view of it
18:03:06 <nirik> oops. I didn't fill it in.
18:03:32 <nirik> or perhaps I did and forgot I did
18:03:36 <smooge> oh it says nirik did
18:04:03 <smooge> I liked how you said you were available most of the time
18:04:20 <nirik> :)
18:04:54 <smooge> ok good times we have: Wednesday 1700 UTC, Friday 1600 UTC , 1700 UTC or 1800 UTC
18:05:45 * smooge tries to figure out how to see which meeting channels are busy when on Friday
18:06:40 * smooge fails
18:07:12 <avij> I have a slight preference towards Wednesday -- Fridays are more probable "travelling around" days for me than Wednesdays
18:07:35 <avij> I'm OK with Fridays as well, if you folks prefer that
18:07:39 <smooge> ok so of those 4 times, which would people really prefer... (aka is meeting on Friday a going to be mostly 3 day we... what avij said)
18:07:40 <nirik> holidays and long weekends also make friday kinda bad
18:07:49 <Evolution> yeah, meeting-free friday is still a goal I hold close to my black little heard
18:07:51 <smooge> ok Wednesday 1700 UTC
18:07:53 <Evolution> s/d/t/
18:07:59 <Evolution> I may not get it, but I like to try
18:08:35 <smooge> #agreed New meeting time is 1700 UTC #fedora-meeting
18:08:46 <smooge> I will put that on the calendar after this meeting
18:09:25 <smooge> #topic Python3x VFAD ?
18:09:58 <nirik> hey, not a bad idea...
18:10:04 <smooge> I would like to propose a VFAD to push through a major update of python3 packages to python37 .
18:10:27 <nirik> well, I talked to python maintainers and they were not keen on 37... they said 36 was there and good...
18:10:29 <smooge> python37 is going to be a 'lts' releaseish so would match EPEL needs better
18:10:42 <nirik> we can ask again, but thats what I heard from them before.
18:10:45 <bstinson> that is something i'd like to participate in
18:10:57 <avij> 37 would likely be a better goal, indeed
18:11:57 <nirik> perhaps after f29 final freeze starts...
18:12:20 <avij> not that I really know anything about this, but a "LTS" sounds good for EPEL
18:12:32 <smooge> Python 3.6 end of life is December 2021 and Python3.7 is no less than 2023-06
18:13:00 <smooge> but I would like to get an idea from python developers
18:13:03 * nirik is just repeating what he was told by the people doing the work
18:13:38 <Evolution> was there a reason 3.7 was bad?
18:13:42 <nirik> lets propose a day and post to the list and ask them about it.
18:13:43 <smooge> no I understand.. the answer usually is 'the one we are about to EOL' and 'the one which hasn't been released yet'
18:14:13 <smooge> When is F29 Final Freeze?
18:14:23 <nirik> well, when I last asked 3.7 just came out and I was told it wasn't worth the bother to build it up in epel... but I could be misrememebring or things could have changes
18:14:42 <nirik> 2018-10-09 starts
18:14:49 <smooge> https://fedoraproject.org/wiki/Releases/29/Schedule ... what nirik said
18:16:12 * bstinson ducks back into a session
18:16:19 <smooge> So How about 2018-10-16
18:16:25 <nirik> in any case whatever stack it is, we can work on fixing things and getting it all working
18:16:38 <nirik> sounds good to me
18:16:56 <smooge> that is a Tuesday so most other go/no-go and other meetings aren't on it
18:17:05 <avij> ok for me
18:17:39 <smooge> not sure if bstinson meant he ducked into something and is offline or something else
18:18:09 <smooge> ok I am going to put that out as a tentative date. We will decide which version of Python we are finalizing on next week
18:19:09 <smooge> #info Tentative VFAD for Python3x big push is 2018-10-16. Suggested version is python37
18:19:21 <smooge> #info however that may change
18:20:01 <smooge> Those were the two items i had on the list
18:20:09 <smooge> #topic Open Floor
18:20:25 <smooge> Anything people have for the open floor today?
18:20:55 <nirik> Not much. Did anyone look more at overlapping packages (I have not)
18:21:03 <pgreco> status on armhfp
18:21:52 <pgreco> I've been working on finishing the packages that were failing
18:22:15 <smooge> yeah.. thanks
18:22:27 <smooge> #topic Removing zabbix20 zabbix22
18:22:29 <pgreco> last weeks releases build without problems, except for "root" which I'm working on failing tests
18:22:50 <smooge> oops sorry .. hit return
18:22:59 <smooge> #topic ARM EPEL Status
18:23:21 <smooge> #info pgreco has been building packages and run into some dead ones
18:23:50 <smooge> pgreco, thank you for doing this.
18:24:00 <pgreco> yeah, no problem
18:24:16 <smooge> #topic Removing zabbix20 zabbix22
18:24:23 <nirik> yeah, root is a giantic thing. ;(
18:24:30 <smooge> OK I forgot about something pgreco found
18:24:40 <smooge> the current zabbix packages are EOL upstream and uninstallable
18:25:11 <smooge> a package which was in either EPEL or EL7 when they were built no longer is in.. so they need to be removed
18:25:54 <nirik> fair enough. Do the maintainer(s) know? I'd say file bugs, wait a bit then retire them?
18:26:18 <pgreco> smooge, if they weren't EOL, we could comment the BuildReq and rebuild without problems
18:26:20 <smooge> ok will check to see if they do. A solution is that zabbix30 will be in the repo soon
18:26:28 <smooge> .whoowns zabbix22
18:26:29 <zodbot> smooge: owner: volter
18:26:32 <smooge> .whoowns zabbix20
18:26:34 <zodbot> smooge: owner: orphan; admin: sharkcz, volter - Fedora EPEL: volter
18:26:51 <smooge> I will contact volter and see what they want to do
18:27:23 <smooge> nirik, to retire them.. open a ticket in releng tracker?
18:27:36 <nirik> yep, or ping me and I can do it.
18:28:01 <smooge> ok will do so
18:28:17 <smooge> I will have a report of the packages overlapping to the lists later today
18:28:30 <smooge> and that is definitely it for my list of things
18:28:47 <smooge> pgreco, I am putting your rebuild in as a standing item in our meetings
18:29:09 <pgreco> smooge, thanks, one thing about that
18:29:24 <pgreco> any chance, in the distant future...
18:29:31 <pgreco> to use koji to build those rpms?
18:29:51 <smooge> that is part of my EPIC proposal and something I need to write up definitive steps on
18:29:58 <pgreco> just to keep them in sync with the others, and testing failure
18:30:16 <pgreco> my theory is on that is something like this
18:30:39 <pgreco> if we have builders, I'd like to rebuild "everything" using my version as a bootstrap
18:30:47 <pgreco> so we don't have to do everything again
18:31:01 <pgreco> and then keep in sync from there
18:31:22 <smooge> we will have to rebuild them somewhere anyway if we are going to sign them.
18:31:36 <pgreco> if something fails in armhfp, that doesn't on other arches, report to the armhfp people
18:31:48 <pgreco> smooge, that is the point
18:32:04 <pgreco> not wasting time bootstrapping, just rebuild
18:32:11 <pgreco> but yeah, that would be the idea
18:32:28 <avij> I'd be happy to see pgreco's packages used as a base for rebuilds, if that's possible
18:32:45 <smooge> yep.. the bootstrapping is useful because it cuts down the 'oh you needed to do X before Y? oh you silly man'
18:33:21 <pgreco> Yeap, that was the main waste of time while doing this
18:33:44 <smooge> it will be useful to know because we will have to repeat this is say someone does a CentOS MIPS
18:34:14 <pgreco> well, hughesjr is working on epel/i686
18:34:15 <smooge> anyway.. the topic and our conversation have drifted off
18:34:23 <smooge> #topic Back to the Open Floor
18:34:54 <pgreco> so we should be able to "refine" the process
18:35:20 <nirik> the trick of the other arches is that the current ones build against rhel and the others would need to build against centos... it's possible, just tricky
18:35:51 <pgreco> right
18:36:17 <smooge> so I will write that up in the definitive steps needed for EPIC that you wanted. And you guys can slap me with wet noodles if it isn't done next week
18:37:17 <smooge> ok I think that is all we have in our brains this week
18:37:30 <smooge> ok for me to call it a meeting?
18:37:43 <pgreco> wfm
18:37:45 <avij> yea
18:37:57 <nirik> +1
18:38:17 <smooge> Thank you again all for coming. See you next week at 1700 UTC
18:38:22 <smooge> #endmeeting