18:00:55 <smooge> #startmeeting EPEL (2019-11-20) 18:00:55 <zodbot> Meeting started Wed Nov 20 18:00:55 2019 UTC. 18:00:55 <zodbot> This meeting is logged and archived in a public location. 18:00:55 <zodbot> The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:55 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:55 <zodbot> The meeting name has been set to 'epel_(2019-11-20)' 18:00:55 <smooge> #meetingname epel 18:00:55 <smooge> #topic aloha 18:00:55 <smooge> #chair nirik smooge tdawson bstinson Evolution pgreco sgallagh 18:00:55 <zodbot> The meeting name has been set to 'epel' 18:00:55 <zodbot> Current chairs: Evolution bstinson nirik pgreco sgallagh smooge tdawson 18:01:10 <smooge> #info this meeting started on time! 18:01:15 * tdawson is here. 18:01:20 <nirik> morning. 18:01:54 <pgreco> hi 18:02:16 <smooge> #info Meeting is run from https://board.net/p/epel 18:02:43 <smooge> #topic Old Business 18:02:52 <smooge> Is there any old business needing to be discussed? 18:04:49 <smooge> #topic EPEL-6 18:04:50 <smooge> #info EPEL-6 is End of Life in 2020-11. It will be moved to archives in 2020-12 18:04:57 <smooge> any other epel-6 items? 18:05:08 <pgreco> not aware of any 18:05:58 <smooge> #topic EPEL-7 18:06:06 <smooge> any EPEL-7 items to discuss? 18:06:57 <pgreco> any ideas to revive the aarch64? 18:07:22 <smooge> tdawson, do you have anything for the python generator items or is that 8 only 18:07:35 <tdawson> smooge: That's mainly 8 18:07:49 <tdawson> But I could bring it up now. 18:08:16 <smooge> pgreco, at this point the only thing I can think of is building aarch64/armhfp/i386 in CentOS Build System somehow 18:08:29 <smooge> tdawson, I will put it on the next topic 18:08:43 <tdawson> ok 18:09:00 <pgreco> smooge, ack 18:09:11 <smooge> #topic EPEL-8 18:09:11 <smooge> #info Python generators (tdawson) 18:09:52 <tdawson> so, the big problem is that python-rpm-generators is already installed when python packages are built, for both epel7 and 8. 18:10:13 <tdawson> And RHEL has the dependency resolution turned off by default. 18:10:20 <tdawson> https://bugzilla.redhat.com/show_bug.cgi?id=1774260 18:11:04 <tdawson> They do not want to change this, since RHEL8 is currently stable. They want us to the the macro in the spec file. 18:11:19 <tdawson> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_basic_system_settings/index#spec-file-description-for-a-python-package_packaging-of-python-3-rpms 18:12:00 <tdawson> Sorry, wrong link 18:12:05 <tdawson> https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_automatically_generated_dependencies 18:12:11 <smooge> tdawson, so we enable this in epel-rpm-macros? 18:12:38 <nirik> we want to disable it no? 18:12:39 <tdawson> That might be what we have to do. 18:12:54 <tdawson> No ... we want to enable it. 18:13:08 <tdawson> We want it to be what it's like in F30+ 18:13:19 <nirik> but if all the rhel8 packages don't use it, doesn't that mean it will be somewhat useless? or do they still generate all the provides? 18:13:55 <tdawson> nirik: It's not the rhel8 packages that are the problem, it's the epel8 (and possibly epel7) packages. 18:14:18 <tdawson> They want to be in sync with their fedora packages, they pull things over, and then their dependencies are all messed up. 18:15:08 <tdawson> From Ken's comment "When we cannot trivially copy work from Fedora 30 into RHEL 8.1, this decreases Fedora's relevance to Red Hat's flagship product (RHEL 8). Mass copy-pasta in .spec files makes RPM packaging more frustrating and less attractive to new developers." 18:15:37 <nirik> sure. I get that, just wondering if enabling in epel8 is only a partial solution... 18:15:38 <tdawson> *sigh* I just realized that was a private converstation. 18:15:56 <smooge> tdawson, me too 18:16:24 <smooge> well they aren't going to enable it in RHEL-8 at all so it would seem to be a partial solution is all we will have 18:16:34 <tdawson> nirik: It probrubly is only a partial solution, but it is affecting us now, and any change in RHEL8 won't happen for at least a year. 18:16:34 <nirik> I guess... we can always try and see. 18:16:55 <tdawson> Yep 18:16:59 <smooge> tdawson, do you want to add it to the macros package or have me do so? 18:17:12 <tdawson> smooge: I'd feel better if I did it. 18:17:28 <tdawson> smooge: I've been testing various things, and I also want to make sure it doesn't conflict. 18:17:47 <smooge> tdawson, I am A-OK with that ! 18:18:22 <tdawson> smooge: If I find I don't have priviledges, I'll ping you 18:18:34 <smooge> okie dokie 18:18:47 <nirik> remember that the epel8 and epel8-playground branches are different... 18:18:57 <nirik> but you have to do a dance to build both. 18:19:18 <smooge> anything else on this subtopic? 18:19:43 <tdawson> Not that I know of. 18:20:14 <smooge> #info sgallagh/merlinm says 18:20:56 <tdawson> I know that merlinm is not here .. don't know if sgallagh is here or not 18:21:29 <smooge> ok I think there was something about stuff sort of moving ahead in staging 18:21:30 <tdawson> I guess I can give an update with as much as I know 18:21:33 <smooge> sure 18:21:53 <sgallagh> I’m not. I’m in a training class this week. 18:21:58 <tdawson> We can currently build modules in staging. I've been working with a multi-step modules (first built this and then built that) 18:22:01 <sgallagh> Can’t split attention. 18:22:11 <smooge> he says while splitting attention 18:22:24 <smooge> oh he crashed 18:22:26 <tdawson> As far as I can tell, the modules are building good, as well as the composes. 18:22:33 <smooge> cool 18:22:48 <tdawson> They are currently working on getting bodhi updates to work with them. 18:23:12 <tdawson> There is currently a bug because the names of the modules are too big 18:23:41 <tdawson> The bug has a patch, they will hopefully deploy that patch to stg this week. 18:24:18 <tdawson> We'll have another week of testing ... and I heard whispers that we possibly might have it deployed to prod on the first week of december. 18:25:19 <tdawson> Don't quote me on that last part, but it was mentioned. 18:25:32 <smooge> cool 18:25:42 <smooge> any questions? 18:26:21 <smooge> #topic Backlog 18:26:21 <smooge> #info https://pagure.io/epel/issues 18:28:51 <smooge> There are currently 45 open tickets. I am hoping to get 1 or 2 done next week 18:28:57 <smooge> That is about it on that. 18:29:03 <smooge> #topic Open Floor 18:29:10 <smooge> anything for the open floor? 18:29:48 <tdawson> Speaking of the backlog of tickets, many of them are missing -devel packages in 8. Do we have an idea on the progress of what we are doing about that? 18:30:41 <smooge> At this point we are waiting to see what rolls out of CentOS-8.1 18:31:00 <tdawson> OK, I was thinking that, but didn't know. 18:31:39 <smooge> once that is outish.. then more on how we get the missing -devel packages comes into play 18:32:04 <nirik> yeah, we really should have a SOP/ process for them... 18:32:15 <nirik> just filing them so we ignore them doesn't do much good. 18:33:44 <smooge> that is my main target for next week... getting an SOP and the backlog dealt with 18:34:43 <smooge> * files 2 tickets to self to do that 18:36:55 <smooge> ok anything else on this today? 18:37:17 <smooge> if not I will call this meeting and we can go about staring at emails and servers which do not boot 18:38:12 <smooge> ok thanks everyone.. see you (well not nirik) next week 18:38:20 <smooge> #endmeeting