22:00:38 #startmeeting EPEL (2021-01-15) 22:00:38 Meeting started Fri Jan 15 22:00:38 2021 UTC. 22:00:38 This meeting is logged and archived in a public location. 22:00:38 The chair is tdawson. Information about MeetBot at http://wiki.debian.org/MeetBot. 22:00:38 Useful Commands: #action #agreed #halp #info #idea #link #topic. 22:00:38 The meeting name has been set to 'epel_(2021-01-15)' 22:00:39 #meetingname epel 22:00:39 The meeting name has been set to 'epel' 22:00:41 #chair nirik tdawson bstinson pgreco carlwgeorge michel_slm 22:00:41 Current chairs: bstinson carlwgeorge michel_slm nirik pgreco tdawson 22:00:42 #topic aloha 22:00:46 aloha! 22:01:00 Aloooha! pgreco 22:01:05 morning 22:01:10 Hi nirik 22:02:41 Sorry, when I hear aloha, I always want to give a loonngg aloha back 22:03:05 * King_InuYasha waves 22:03:09 .hello ngompa 22:03:10 King_InuYasha: ngompa 'Neal Gompa' 22:03:18 Hi King_InuYasha 22:03:54 howdy yall 22:04:03 Hi carlwgeorge 22:05:32 So, michel_slm said he possibly wouldn't be here, but he gave me his summary for the EPEL Packaging SIG 22:05:56 "not much to update on epel-packagers except the one non-responsive check I filed got resolved, maintainer didn't have time for Fedora and is orphaning packages" 22:06:37 Did anyone have anything else to say about epel-packagers ? 22:07:22 not here 22:07:26 OK, moving on to epel8-next 22:07:40 carlwgeorge: What is the status this week? 22:08:35 got a pull request started for fedscm-admin to support epel8-next, but it looks like i need to redo it for the master>main change https://pagure.io/fedscm-admin/pull-request/55 22:09:07 next up will be a branch check to ensure that epel8 exists if epel8-next is requested 22:09:12 shouldn't be too much overlap I would hope 22:09:30 yeah i should just be able to rebase off main and resubmit 22:10:26 nirik, you submitted a request to delay the move, right? 22:10:49 yeah, our fedscm-admin and fedpkg changes weren't done... want to get them released and out 22:11:10 carlwgeorge: oh, just to change your pr? you can just edit it and change it. 22:11:23 or I can if you want. in the web interface. 22:11:44 just edit and change the target branch. Pagure lets you do that no problem now 22:12:00 oh sweet, i had heard that feature was coming (changing target branch) but i didn't realize it was live on pagure.io 22:12:53 yep 22:12:56 part of pagure 5.12 22:13:45 besides the branch check in fedscm-admin, i need to go through fedpkg and look at a few things to make sure it works with epel8-next branches 22:13:56 was hoping to do that this week but ran outta time 22:15:22 that's it from me 22:15:45 Sounds good, and great progress 22:16:16 There are two other things from last week, but I'm going to keep them in their EPEL7 and EPEL8 topics. 22:16:23 #topic EPEL-7 22:16:57 Last week we talked about python3 vs python36 in EPEL7. There was going to be an email to continue the discussion. Did that ever get sent? Or did I just miss it? 22:17:15 * nirik didn't see anything on it 22:17:15 that was me, ran outta time on that one too 22:17:30 Ah, OK. Not a problem. 22:17:44 Did you want to talk about it here more? Or should we just wait for the email? 22:18:04 i mean i'm open for comments if anyone has any 22:18:26 but i think i have all the info i need for the initial email, which i have a rough draft of started 22:18:41 I could go either way, so I was waiting for the email ... I'm fine waiting. 22:18:51 * King_InuYasha is waiting on the email 22:19:20 Were there any other EPEL7 things to discuss? 22:19:27 i suck at email, but i'll try to get it out before the next meeting so we can discuss the feedback it generates 22:19:49 carlwgeorge: Ya ... but you are good at so many other things. :) 22:20:50 OK, moving on to EPEL8 22:20:55 #topic EPEL-8 22:21:38 Last week we were discussing the problem with new packages in RHEL, that are also in EPEL, and how this is/will affect Stream 22:22:40 If I remember, we didn't really have much of a resolution, or even felt if there was much we could o. 22:22:46 do. 22:22:46 i think we settled on being fine with it until the new package is released in rhel ga 22:23:04 yeah, I think it is the "less bad" option 22:23:12 yup 22:23:22 my proven packager looks likely to be approved so after that happens i'll start retiring the ones that were added in 8.2 22:23:27 if we could have some sort of alarm about it, it would help, but don't even know how to do that 22:23:29 there's fancy dnf magic we could do if we need it more 22:23:53 but I don't know how often this happens that we would need it 22:23:59 #info If a new package comes into RHEL that is also in EPEL. We will "be fine with it" until the new package is released in RHEL GA. 22:24:09 We might also ping internally... since there's supposed to be EPEL checks, but they never seem to happen 22:25:08 Ya, I'm hoping the new gating checks start catching these issues more. 22:25:32 OK, well, that subject didn't take as long as I expected. 22:25:35 well, last cycle (e.g. RHEL 7), it didn't happen too often 22:25:50 I don't know if we expect to happen more with RHEL 8? 22:26:54 At this point, I think things are starting to slow down. But I'm sure we'll get a few more. 22:26:59 blech, I mean i.e., not e.g. :P 22:27:05 which? new packages in a minor release? or them notifying epel maintainers about it? :) 22:27:18 new packages pulled from EPEL in minor releases 22:27:25 they never notify EPEL maintainers 22:27:34 I've learned that lesson in EPEL 6 and EPEL 7 22:28:03 They did for a short while... but something failed or they stopped knowing they were supposed to or something. 22:28:34 hmm, maybe I just got unlucky 22:29:12 it wasn't too long they were doing it. around 7 GA... but anyhow. 22:29:24 the biggest problem for that is when they do it with an older ENVR 22:29:40 or with less functions than epel, requiring a supplemental package to keep up 22:30:07 Yep 22:30:17 well, the thing was they were supposed to open a bug and tell the epel maintainers... hey, I am going to land foo-1.1-1 in rhel x... you will need to retire your version,e tc. 22:30:21 Anything else EPEL8 related? 22:30:43 so then the epel folks could say 'no, you need a better release/version' or 'you are breaking foo' 22:31:28 do we need to explicit mention this in the epel guidelines? 22:31:35 *explicitly 22:31:40 Hmmm ... I know where the internal documentation is for that ... maybe a pull request to it would get that back into the workflow. 22:32:10 nirik, that's utopic, I guess, but it would be great 22:33:34 tdawson: I have no idea where it is. I would just complain... but if you know, awesome! put it back in. ;) 22:34:31 Ugg ... that section is huge :( ... it's a wonder any new packages make it in. 22:35:15 * King_InuYasha wonders if RHEL has _too much_ process 22:36:54 Honestly, most of it is legal checks ... but ... anyway, I'll take a look, see if I can add anything about epel. They have a process for adding stuff now, and at least a ticket and/or bug and/or pull request would get someones attention. 22:38:04 Anything else for EPEL8? 22:39:02 nope 22:39:04 tdawson: let me know if I can help any/nag people. 22:39:16 nirik: Will do 22:39:22 #topic General Issues / Open Floor 22:39:45 We actually made it to the Open Floor this week. 22:40:16 hurray 22:40:19 yeah! 22:40:32 this is good, I need my weekend to start yesterday :D 22:40:42 Does anyone have anything for the open floor? Or are we ok ending early? 22:40:54 I need it to stop being the 2020 bonus round. ;) 22:41:40 Just two more months and the 2020 bonus round is over. Ya!! 22:41:52 I think we're ok, at least I am 22:42:02 thanks guys! 22:42:11 I've got nothing :) 22:42:17 Thank you everyone, for being here and for the good (and short) discussions. 22:42:31 We'll talk to you all next week. 22:42:37 #endmeeting