22:01:11 #startmeeting EPEL (2021-03-05) 22:01:11 Meeting started Fri Mar 5 22:01:11 2021 UTC. 22:01:11 This meeting is logged and archived in a public location. 22:01:11 The chair is tdawson. Information about MeetBot at http://wiki.debian.org/MeetBot. 22:01:11 Useful Commands: #action #agreed #halp #info #idea #link #topic. 22:01:11 The meeting name has been set to 'epel_(2021-03-05)' 22:01:12 #meetingname epel 22:01:12 The meeting name has been set to 'epel' 22:01:14 #chair nirik tdawson bstinson pgreco carlwgeorge michel_slm 22:01:14 Current chairs: bstinson carlwgeorge michel_slm nirik pgreco tdawson 22:01:15 #topic aloha 22:01:31 hey 22:01:32 morning 22:01:33 hi 22:01:35 * carlwgeorge waves 22:01:38 Hi nirik 22:01:40 Hi pgreco 22:01:43 Hi carlwgeorge 22:02:37 I've just ogtten back, and haven't read any emails for a week ... so I'll run the meeting, but have no knowledge of anything going on for a week. 22:03:15 I don't think we have much news 22:03:30 yeah, not much 22:04:09 I'm ok if it's short :) 22:04:11 no progress on my tasks 22:05:28 So, epel8-next, still where it was? correct? I believe we're waiting on permissions? 22:05:32 * pgreco checks the url for time slot voting 22:06:16 i need to get fedpkg into shape on handling epel8-next branch requests, specifically how it's going to check if a package is in stream to not allow it in epel 22:07:21 Ahh ... ya, I'd forgot that we need to check stream in addition to regular RHEL. At least for epel8-next. 22:07:26 that involves fedpkg and an ansible role called repo2json that generates some json about rhel packages. i haven't determined yet if the stream package info should go in the same file or in a different file. 22:07:29 we could just make that a 2.0 issue... I mean, it's not likely to happen too much? 22:07:56 probably not 22:08:18 Related to that, I put in a request to change the email that is sent (when RHEL adds a package that is in EPEL) to a bugzilla. They accepted it, and are working on it. 22:09:07 How far along they are, I don't know, as I said, I haven't read emails for a week, but I saw it right before I left. 22:10:24 OK, moving on to EPEL packaging SIG 22:10:50 Hmm ... michel_slm isn't (or shouldn't) be here ... anyone know of any progress on that? 22:11:20 there should be a minion reporting in michel_slm's place :P 22:12:23 at least, that's how filbranden described himself 22:12:31 Yep ... but I don't see either of them. 22:12:46 We can skip that for this week I guess. 22:14:20 * King_InuYasha waves 22:14:21 For documentation, I found out the correct person to ask about getting a base EPEL directory in fedora docs, but that also was right before I left, and didn't contact them. 22:14:22 .hello ngompa 22:14:23 King_InuYasha: ngompa 'Neal Gompa' 22:14:25 Hi King_InuYasha 22:15:41 Let's see, other old business was voting for a new time slot. 22:16:10 I pretty much can only come to this slot :( 22:16:27 my team is moving to no-meetings-fridays, so a new time slot is welcome 22:17:00 I'm moving to a new team ... and haven't met with them yet, so I haven't voted yet, cuz I really don't know what's open for me. 22:17:36 we can let it ride a bit more and see what we end up with? 22:17:52 Are we ok keeping this time slot for at least one more week? ... as nirik said. :) 22:18:13 sure 22:18:58 King_InuYasha: We'll keep your time slot in mind ... do you mind filling out a line in the poll? Or do you want me to fill it in for you? 22:19:47 tdawson: please fill it in for me 22:19:51 King_InuYasha: Will do 22:20:10 OK, so we'll give it one more week, if we feel we're good next week, we'll vote on it. 22:20:12 I actually would prefer another day, but I don't have anymore days left except weekends 22:20:37 carlwgeorge has seen my calendar and knows what I'm talking about, so when I say I don't have room, sadly I mean it :( 22:21:34 I think that's it for old business ... 22:21:40 #topic EPEL-7 22:22:15 Bring something up if you know of anything. Since I haven't checked anything this last week, I don't know. 22:23:28 I'll take the silence for "move on" 22:23:31 yeap 22:23:36 I have something for 8 22:23:37 #topic EPEL-8 22:24:11 today I realized that dwarves is still available in epel8 22:24:35 I think I know the guy who filed the retirement bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1833561 22:25:23 Oh ... I didn't know it was in EPEL8 ... ya, we need to get that retired. 22:26:55 luckily, it is older, but I see centos' version in powertools so many people may have it installed from epel yet 22:26:56 Good thing is, looks like RHEL8 version is newer than epel8 ... but still need to retire it. 22:27:12 i forgot about that bug 22:27:17 Ha! ... my typing is still slow. 22:27:35 i have provenpackager now so i'll just retire it myself 22:28:17 carlwgeorge: That would be good. Thank you. 22:28:22 Anything else for EPEL8? 22:29:14 not here 22:29:22 #topic EPEL-9 22:29:49 I skimmed email subjects and saw there was something on this ... I haven't read it yet. Is there anything to discuss at this point? 22:29:52 there was some discussion about this on the fedora devel list. ;) 22:30:02 not really I don't think... 22:30:09 I don't know if I'd be on board with auto-branching for EPEL9 22:30:52 Oh, it's for auto-branching ... hmm ... I'll have to read it before I have an opinion. 22:30:53 I still don't see how it would work. :) 22:31:07 -1 on auto branching 22:31:55 So, looks like three "no's" on it ... not looking good for it 22:32:04 Although that doesn't mean there won't be discussions. 22:32:14 yeah, without more info, I'm a -1 too 22:32:31 maybe there is a solution there, but I'm not seeing it 22:33:22 it's signing up people for a nontrivial amount of work 22:33:36 unlike Fedora, RHEL releases are *big* jumps 22:34:10 for those who keep a single "main" branch, it shouldn't be bad 22:34:23 but not everybody does that 22:34:40 I think the ELN stuff should help *some* of that, but there are still 10's of thousands of packages that don't get touched by ELN. 22:35:44 Well, it sounds like pretty much everyone (but me, cuz I haven't read it yet) is against it. No point it redoing the discussion here ... I'll move on. 22:36:06 #topic General Issues / Open Floor 22:36:26 * nirik has nothin 22:36:38 Does anyone have any idea when CS9 binaries will start becoming available? 22:36:47 yes 22:37:43 carlwgeorge: Are you able to share that information? It's ok if it's no. 22:37:52 honestly not sure 22:38:03 King_InuYasha can probably guess and be pretty close 22:38:48 I'm thinking is sometime before the end of May 22:39:13 the problem right now is planning how to message it, so we don't get further raked over the coals about stream being a beta for rhel 22:39:24 ugh 22:39:26 right, there's that 22:39:55 let's just say people don't like me saying it will have a 6 year lifecycle, like i have been doing 22:40:33 the announcement you'll probably see is something like "CS9 is now open for contributions", which will also be around the time there will be consumable artifacts 22:40:38 *say 22:40:52 carlwgeorge: But that's the official thing now ... well maybe not "6 year livecycle" but "during the Maintenance RHEL period" 22:41:33 call it "beta centos stream", so people can't say this is the beta for RHEL if that's already the beta for something else 22:41:34 that's 5 years, but i haven't been shy about pointing out cs9 will be available approximately a year before rhel9, and i can do math 22:41:43 :) 22:42:11 1+5 is not the same as 6 according to some people :P 22:42:20 carlwgeorge: I feel you.... 22:42:23 misc: i actually suggested that ("how can there be a beta of a beta"), but it sounds like we are going to avoid any and all terminology that is similar to rhel the product 22:43:28 :/ 22:43:51 in reality, cs9 will be a little rough at first, because it will be an early preview of 9.0. some people will try it, claim it's evidence of it being unstable, and give us even more shit. 22:44:13 So, last time I checked, which was last week, we couldn't even start with the first test package being built. And until you have the infrastructure in place enough to build a single test package, it's really hard to have an estimate of when things will be available. So, to answer the original question, I think King_InuYasha's guess of end of April, sometime in May, is as good a guess as any. 22:44:14 if you normally avoid rhel x.0 releases, you probably don't want to use cs9 in the first year-ish 22:44:16 reuse debian naming convention or something ? 22:45:11 (Centos stream director cut) 22:45:18 we could use codenames :P 22:46:07 CS 9.-1 , because -1 is before 0 22:46:19 *laughs* 22:46:41 CentOS Stream 9pre with codenames after great rivers :) 22:46:59 Stream Styx 22:47:21 CS9.1AD 22:47:36 Because the Stream Styx leads into RHEL 22:47:52 ah ah 22:47:58 Sorry ... my puns are as good as smooges. :) 22:48:20 oh god 22:48:23 that's good XD 22:49:13 Anyway ... I don't mind continuing with this, but is there anything else anyone has? 22:50:29 I'll take the silence for a no 22:51:32 Thanks for coming everyone. We'll talk to you next week, same time, same place. But hopefully we can vote then, and have same place, different time. 22:51:33 time for the weekend 22:51:52 #endmeeting