18:00:40 #startmeeting EPEL (2019-06-19) 18:00:40 Meeting started Wed Jun 26 18:00:40 2019 UTC. 18:00:40 This meeting is logged and archived in a public location. 18:00:40 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:40 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:40 The meeting name has been set to 'epel_(2019-06-19)' 18:00:40 #meetingname epel 18:00:40 The meeting name has been set to 'epel' 18:00:41 #topic Chair and Introductions 18:00:41 #chair bstinson Evolution nirik smooge pgreco tdawson 18:00:41 Current chairs: Evolution bstinson nirik pgreco smooge tdawson 18:00:41 #topic Agenda 18:00:42 #info EPEL-8 Status 18:01:10 I have the wrong date in the title.. but hello people 18:01:20 hi all 18:01:20 hello 18:03:31 ohhh, a fewe minutes late, but I'm here 18:03:54 and I even started it at the right time this week 18:05:05 ok this week is pretty short I think. [My wife says I look like death warmed over and my kid has come down with the cough I had Monday] 18:05:13 #topic EPEL-8 18:05:13 #info Looking to send https://hackmd.io/@ssmoogen/rysKDi01H to lists and blog 18:05:13 #info Need feedback on https://hackmd.io/@ssmoogen/B1p2QM-eS 18:05:13 #info Started on https://hackmd.io/@ssmoogen/SymTjXZgr 18:05:14 #info Have one more doc to write. 18:06:19 * tdawson is also here, sorry for being a bit late. 18:06:28 my main ask is for people if they have anything they think needs to be added changed. I just started the second doc so it probably needs the most work and the third one is really really really raw 18:06:46 * nirik hasn't read the second or third one yet 18:07:53 yeah not expecting people to do so.. it is more of a ehads up 18:08:59 well, I plan to, just haven't yet. ;) 18:09:12 smooge, doc2 known issues, point 1 18:09:33 that could be fixed via platform-python also, right? like I did for htop 18:10:16 so I am not sure which packages are meant to use platform-python and which shouldn't 18:10:16 No, using platform-python instead is a "bad idea" 18:10:39 tdawson, why? so I can fix htop properly 18:11:13 it only contains some of the functionality of pytho 18:11:22 ^^ 18:11:40 it is supposed to be just enough to make yum and other system tools work 18:11:42 which seems to be enough for htop, but understood 18:12:06 Why do you not want to use python3 or python2? 18:12:27 probably because you then have to assume the user wants that 18:12:53 and also, it is not available yet in my c8 test 18:12:58 if possible, python3 should be preferred. 18:13:00 and platform-python is :D 18:13:37 I decided not to mention it as something to use and would prefer if any tests we put in place point it out if used. 18:13:52 however I understand why some utilities will want it 18:14:23 FWIW, ansible is planning to use it. 18:14:37 ok, then I'll change it to python3 along the road, if it creates problems 18:16:52 I am expecting this is going to be a large pile of exceptions.. 18:17:10 I added a 5 to cover that 18:17:51 smooge, ack 18:18:35 also how would people like these to be published? And what other documents would people like/expect? 18:20:10 One comment on comment two ... thus far, I haven't had any problems with switching packages from python2-sphinx to python3-sphinx ... but, I could just be lucky in that respect. 18:20:43 probibly with the other epel docs... so probibly we should talk to the docs folks. 18:22:20 tdawson, there was a bunch of reports of broken packages in rawhide due to sphinx3 18:22:58 It might be old news on my part and could be dropped. 18:24:16 nirik, ok will do so. 18:24:22 One other known issue "Sometimes RHEL8 only has a python3 package for a dependency you need for your build. (Example: python-bleach requires python2-html5lib, but RHEL8 provides only python3-html5lib). You have two choices. 1 - Choose not to have the python2 part of your package. 2 - create and support a python2 version of the package you need (Example: python2-html5lib)" 18:24:55 smooge: python2-sphinx was dropped because it was python2. That broke a lot of things that used it, they needed to move to python3-sphinx. 18:25:38 we should discourage python2 packages probibly... 18:26:23 For my fedpkg dependencies (alot of python stuff), I removed the python2 parts. 18:26:46 But, I want to leave the option open if others really need their python2 stuff. 18:27:02 nirik, I know why python2 was dropped. There were emails on the lists about moving to python3-sphinx for some kde and other packages breaking the builds 18:29:03 however those were fixed looking at the bugzilla 18:29:55 smooge: What you have written is fine. I'm sure some people are going to run into the python3-sphinx problem. I just wanted you to know that I haven't hit is yet. 18:30:18 sure, I mean python2.7 will be in rhel8 until 2024... but less and less upstreams will care about it or support it, etc 18:31:58 ok added those items 18:32:23 brb 18:36:04 #topic Open Floor 18:36:25 I don't have much else today.. does anyone else? 18:37:19 Do you think we are still on for the first of July ? 18:37:34 Err ... not for the final release, but ... I forget what we call it. 18:37:55 so next week because it is mostly US and other holidays will just be me documenting and putting out all the lessons learned 18:38:10 beta? 18:38:17 "soft opening"? 18:38:50 Ohh ... I like "Soft opening" ... mainly cuz beta epel sounds odd. 18:39:05 the week after that will be putting all the changes into production and doing the branch builds for the core packages 18:39:37 * nirik notes we used beta for epel7, but whatever, I don't care. 18:39:38 the core packages being epel-release,epel-release-macros, fedpkg-minimal, fedpkg, and ... 18:40:26 do we have other core packages needed? 18:40:45 I think fedora-packager was also a core package 18:40:58 yeah 18:41:33 for those and the initial bringup/soft open we should not use bodhi either... or else we will drown in overrides 18:42:11 ok I need to document that in the plan because that hadn't been brought up before 18:42:49 I think it will make the initial seeding of things easier on everyone... 18:43:00 I don't disagree. I didn't think of it at all 18:43:35 also another thing would be how to get f28 packages for any bootstrapping? 18:44:06 there are things which need itself to build and the previous one which should work would be the f28 one 18:44:38 in fedora there's a process for that... 18:44:41 * nirik finds link 18:45:17 https://docs.fedoraproject.org/en-US/packaging-guidelines/#bootstrapping 18:45:43 so basically should be conditional in the package spec... 18:47:33 ok thanks will add that to the document 18:48:02 i remember that Dennis had to do some F18/19 packages for RHEL-7 in certain bootstrap issues 18:48:13 but not sure what the process was 18:49:04 ok I think we have all we have for this meeting. Thank you all for the feedback and points that I need to cover 18:49:23 I will post the first document on my blog and the mailing list shortly and then put the rest in the pagure docs 18:50:22 oh I think next week is not a holiday 18:50:31 but do not expect too high of attendence. 18:50:41 #info Have a good week and thanks for the fish 18:50:44 #endmeeting