20:00:13 #startmeeting EPEL (2021-09-08) 20:00:13 Meeting started Wed Sep 8 20:00:13 2021 UTC. 20:00:13 This meeting is logged and archived in a public location. 20:00:13 The chair is tdawson. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:13 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:00:13 The meeting name has been set to 'epel_(2021-09-08)' 20:00:14 #meetingname epel 20:00:14 The meeting name has been set to 'epel' 20:00:14 #chair nirik tdawson bstinson pgreco carlwgeorge michel dcavalca 20:00:14 #topic aloha 20:00:14 Current chairs: bstinson carlwgeorge dcavalca michel nirik pgreco tdawson 20:00:19 morning 20:00:38 Hi nirik 20:01:07 hello 20:01:20 Hi pgreco 20:02:24 .hi 20:02:25 carlwgeorge: carlwgeorge 'Carl George' 20:02:32 Hi carlwgeorge 20:02:42 hello 20:02:50 Hi ssmoogen 20:03:57 We're starting off a little slow today ... give it another minute or so and see if dcavalca shows up. 20:04:29 I'll start with a rather OT while we wait ;) 20:04:38 Sure 20:04:55 nirik, are you aware of any issues in mirror management last night? 20:05:23 suddenly all my CI was failing due to error 503 and other similar things while downloading updates 20:05:23 there was indeed a 'event' where our proxies all ran out of disk space for a short time. ;( 20:05:40 yep. Sorry about that. I still am not sure of root cause, but will be looking more 20:05:46 And ... times up :) Although you can finish that if you want, but I'm going to start. 20:05:57 #topic Old Business 20:06:06 Let's start with epel-next 20:06:10 np, just wanted to know, thanks 20:06:18 carlwgeorge: nirik: Any news on -next ? 20:06:23 yes 20:06:33 Ya!! 20:06:36 https://koji.fedoraproject.org/koji/buildtargetinfo?targetID=20514 20:06:47 Cool! 20:06:49 the tags and build target for epel9-next exist 20:07:04 So I could do some scratch builds? 20:07:08 the signing key also exists. 20:07:09 also the gpg key for epel9 and epel9-next 20:07:19 Cool!! 20:07:27 tdawson: probably, i think a scratch build will work 20:07:42 still plenty of other pieces to wire up, but this is the first significant progress i'd say 20:08:43 That is some great progress though. Thank you to everyone who got that going. 20:09:11 nirik and mboddu are my heroes 20:09:21 nirik++ 20:09:38 carlwgeorge: ++ 20:09:44 next step will be figuring out the json for the valid_epel_package check in fedscm_admin 20:11:19 that's it, we can move on 20:11:31 Sounds good, and thanks to all three of you. 20:11:49 Does fedpkg know about epel9-next yet? 20:12:20 I'm guessing not, but I was just wondering if it's wildcarded. 20:12:40 it's a wildcard, fedpkg shouldn't need an update 20:12:50 awesome 20:12:55 in theory (famous last words) 20:12:59 Ha! 20:13:15 Moving on to documentation, which should be fairly quick. 20:13:50 I changed some of the wiki pages to redirect to the corresponding EPEL docs pages in Fedora docs. 20:14:22 I stopped when I realized there were some translated pages, and we didn't have any of those in the EPEL docs area. 20:15:06 I'll get those up this next week. Plus Petr Bokoc said that EPEL should go on the front page of Fedora Docs. So also, expect that this next week. 20:15:37 hell yeah 20:15:45 :) 20:15:47 oh it's already there 20:15:58 hmm, but with a broken link 20:16:24 Ha! ... ok, I'll let him know the link is broken. 20:16:48 yeah it ends with "fedora-epel" instead of just "epel" 20:18:18 I think that's it for documentation. I think next week we'll take it off the agenda. 20:19:00 So, should the "CPE to staff EPEL work" go in the old business? or Open Floor? 20:19:01 thanks for all your work on that, looking forward to be able to update the docs with prs instead of wiki syntax 20:19:15 tdawson++ 20:19:35 open floor i think, as i don't think we've discussed it here before 20:19:48 Ok, then we have a topic for open floor. 20:20:40 The "bugzilla's for RHEL packages replacing EPEL packages" is now implemented ... we'll have to see how it works with the next package that does that. 20:21:44 i'll keep an eye out 20:21:59 They do not currently block the tracker I setup. That was another feature, and I'll let ya'll know when it's implemented. Meanwhile if you see a bug for removing an EPEL package, you can link it here - https://bugzilla.redhat.com/show_bug.cgi?id=1998160 20:22:10 the last two packages i added to the c8s compose were fedora only so far, so not applicable 20:22:46 OK 20:23:16 No progress on badges, logos and mascott ... I'll give them a ping this week. 20:23:50 I think that's it for Old Business. 20:23:58 #topic EPEL-7 20:24:41 Anything for EPEL 7 this week? I don't think I saw anything. 20:25:39 #topic EPEL-8 20:26:26 #topic EPEL-Packaging-SIG 20:26:41 We're zipping right along ... anything for the Packaging-SIG ? 20:26:58 there was the ticket filed by ceph maintainer? 20:27:15 That's right. 20:27:29 https://pagure.io/epel/issue/121 20:28:15 That would be nice if he maintained those in EPEL ... get some more packages in there. 20:28:33 yeah, I am definitely +1. 20:28:50 as long as they don't mind the sig updating and poking at the deps 20:28:57 i'm happy to have help in the sig, but i'm not clear how being in the sig makes things different for that maintainer 20:29:16 i'm assuming he's the fedora maintainer, so he can just request the branches and go 20:29:37 carlwgeorge: Actually, there is the EPEL SIG, and the EPEL Packagers SIG ... it sounds more like he just wants to be an EPEL packager. 20:29:50 I've learned alot while doing the documentation :) 20:29:53 yeah i think it's a misunderstanding of the scope of those 20:30:06 well, it helps them by having the sig co-maintain all their deps 20:30:26 Yep ... do we know if he's a fedora packager or not? 20:31:10 https://src.fedoraproject.org/user/kkeithle/projects 20:31:33 yes, long time packager. 20:31:56 so what is the epel sig for? 20:32:12 i understand the purpose of the epel packagers sig, i think 20:32:27 The EPEL SIG is technically, everyone working on the EPEL project. EPEL is technically a SIG. 20:32:33 we are the epel sig. ;) 20:32:55 But the SIG part was dropped from normal conversation many years ago. 20:32:55 but functionally, what does being in the epel sig group (what the ticket is asking for) give a person? 20:33:28 it used to be a formal membership 20:33:33 if the group isn't actually used for anything, we can just reply to the ticket and say "congrats you're in the sig" :D 20:33:39 I perhaps misunderstood the ticket as well... I thoguht they were talking abotu epel-packager-sig 20:34:04 perhaps we could invite them next week? but yeah, can ask for clarification in the ticket 20:34:19 so long ago, SIG membership was something groups controlled with specific requirements. 20:34:33 like to become an ambassador and similar things in Fedora 20:34:45 Well, he doesn't own (fedora own) any of the 100+ packages he wants to maintain. So there is going to have to be a process to get those in. I think we mainly just need to guide him to the steps. 20:35:07 yeah, stale package requests and such 20:35:13 err, stalled 20:35:14 that was back when we were a 'sub-project' versus a SIG. 20:35:56 I can ask for clarification in ticket and invite them next week? 20:36:01 yes 20:36:10 nirik Yep, sounds good. 20:37:07 I think I need to write a "What is the different between EPEL SIG and EPEL-Packagers-SIG" in the FAQ. 20:37:14 +1 20:37:39 Anything else for this issue? 20:38:11 And, any other Packagers SIG things to talk about? 20:38:31 is https://fedoraproject.org/wiki/EPEL/Packagers moving to the new docs? 20:39:12 ah i found it, nevermind, just didn't have a redirect from the wiki page 20:39:16 https://docs.fedoraproject.org/en-US/epel/epel-packagers-sig/ 20:40:36 Done 20:40:56 Ok, moving on to open floor 20:41:07 #topic General Issues / Open Floor 20:41:27 ok so what about this announcement that CPR is running EPEL :)? 20:41:35 HA!! 20:41:54 Here is our official announcement - https://lists.fedoraproject.org/archives/list/epel-announce@lists.fedoraproject.org/thread/5AHOWUXWUIOJGSA5BAEAMNL3UDZISTXJ/ 20:42:16 I hear they are hiring some hot shot developers and such 20:42:34 I wish the FLOCK / Nest video's were up, cuz I did talk about this. :) 20:42:43 ssmoogen: Only the best. 20:43:01 * carlwgeorge grins 20:43:26 it's welcome news for sure. :) 20:43:31 so I want to thank you all for getting this over the line 20:44:32 ssmoogen: Well, you carried the ball all these years, we just got it over. So thank you. 20:44:54 Before we go too much further, is there anyone here that wants more details? 20:45:08 sure, i can add some details 20:45:21 carlwgeorge: go for it. 20:46:20 basically rhel8 adoption isn't where the business expected it to be at this point. customers are explicitly telling red hat that a major reason is lack of epel8 packages they depend on. the business unit wants to avoid a repeat with epel9. 20:46:40 * ssmoogen keeps his mouth shut 20:47:14 if only someone had warned them about this sooner :P 20:48:40 so what this boils down to is instead of cpe members working on epel stuff in their spare time, a few of us will get to work on epel primarily as part of our official duties. that combined with epel9-next will hopefully set up epel9 for success. 20:49:50 i think that covers it, but of course if anyone has additional questions feel free to hit me up 20:50:49 Any other questions? 20:51:02 good luck. I would recommend a couple of bottles of Everclear with some "Old Grand Dad" to water it down 20:51:34 One note. The EPEL Committee Chair will not be a paid position, it will continue to be ... what it is today. 20:51:53 ah crap there goes my plan for world domination 20:51:59 Ha! 20:52:01 right. the community will stay the way it is... CPE person will work with community within the community framework 20:52:11 Yep 20:52:26 ssmoogen: you kid but i did see a hot take online that this was a power grab by red hat to control epel 20:52:49 hahahahahahhahahahahah 20:52:52 hahahahahahahahahahhahaha 20:52:54 people... are ill informed 20:52:58 <<<>>> 20:53:01 Ha! 20:53:21 let me find the link, so you can laugh as you face palm 20:53:26 the phoronix comments are... particularly ill informed 20:53:26 I am glad I didn't see it.. my return comment would be 'you are an idiot' 20:53:36 no I really don't want to see it 20:53:56 nirik guess correctly 20:54:01 *guessed 20:54:04 I would be too tempted to reply 20:54:32 https://www.phoronix.com/forums/forum/software/distributions/1276832-red-hat-looking-to-bolster-epel 20:54:37 sick em smooge 20:54:43 * carlwgeorge grabs popcorn 20:54:56 nope. sorry no need. You said it was on Phoronix. 20:54:56 * nirik waits for epel to be aquired by rh so he can cash out. 20:55:15 *laughs* 20:55:51 OH one last item 20:55:53 I don't mind keeping going, but is there any other open floor items? 20:56:03 ssmoogen: Sure 20:56:40 did we do a 'does it install?' on EL7 lately? Someone was wanting to get zbar into EPEL because they use it on EL7, but it doesn't look like that package installs anymore 20:57:07 it is in the repo, but some dependcies or such aren't there 20:57:31 I haven't done it for a while. I sorta figured we haven't released another RHEL7 release, so things should still work. 20:57:36 I realized I hadn't done this in a looooong time so it fell in the cracks 20:57:54 But I can. I still have my script. 20:58:37 zbar seems to be used a lot in various things from AI training to backup controls for bar-readers 20:59:17 getting it into EPEL-8 is a chore as it needs GraphicMagick and some other things 20:59:30 looks like it hasn't been rebuilt in 5 years for epel7 21:00:08 anyway.. saw that and thought I should bring it up in the meeting if I remembered. 21:00:08 it would be nice if we ran this on a schdule like the fedora one 21:00:30 nirik Yep. 21:00:31 sounds like something to be added by the new CPR team 21:00:43 ssmoogen: It installs on my centos7 machine. 21:01:39 nirik That is top of my list of things I want to do after kde. 21:01:53 cool 21:02:02 hmm will have to ask Mr Bowling what was broken then 21:02:27 Oh ... looks like we are out of time. 21:02:41 Thank you everyone for coming, contributing, and the good discussions. 21:02:50 We'll talk next week, if not sooner. 21:02:59 thanks for running things tdawson! 21:03:03 later yall 21:03:03 #endmeeting