20:00:15 #startmeeting EPEL (2021-04-28) 20:00:15 Meeting started Wed Apr 28 20:00:15 2021 UTC. 20:00:15 This meeting is logged and archived in a public location. 20:00:15 The chair is tdawson. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:15 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:00:15 The meeting name has been set to 'epel_(2021-04-28)' 20:00:17 #meetingname epel 20:00:17 The meeting name has been set to 'epel' 20:00:18 #chair nirik tdawson bstinson pgreco carlwgeorge michel_slm 20:00:18 Current chairs: bstinson carlwgeorge michel_slm nirik pgreco tdawson 20:00:20 #topic aloha 20:00:30 morning all 20:00:40 hey everybody 20:00:55 I wasn't sure who was going to be in today, due to the summit 20:01:00 Hi nirik 20:01:02 Hi pgreco 20:01:26 .hi 20:01:27 dcavalca: dcavalca 'Davide Cavalca' 20:01:35 There wasn't anything this late in the day that I wanted to watch on the Summit, so I'm good. 20:01:39 Hi dcavalca 20:01:39 hello 20:01:58 Whoa ... who is this SSmoogen :) 20:02:03 Hi SSmoogen 20:02:24 .hello salimma 20:02:25 michel_slm: salimma 'Michel Alexandre Salim' 20:02:34 Hi michel_slm 20:02:43 see, I'm not over-eagerly early this time 20:02:53 *laughs* 20:03:03 really like the logo refresh finally making it to Matrix 20:03:21 Nor are you late 20:04:16 fashionably on time 20:04:39 Which reminds me ... is carlwgeorge going to make it? 20:04:48 just barely 20:04:50 * carlwgeorge waves 20:04:58 Hi carlwgeorge 20:05:14 #topic Old Business 20:05:27 Let's start with the EPEL Packaging SIG 20:06:29 I spent some time going over stuff that we'd backported internally from Fedora for c8s 20:06:44 we'll probably be filing more tickets to get packages branched for EPEL in the coming weeks 20:06:48 e.g. I just did https://bugzilla.redhat.com/show_bug.cgi?id=1954817 20:07:07 I'm also still waiting on some progress on https://bugzilla.redhat.com/show_bug.cgi?id=1942748 20:07:34 Does anyone know if the bodhi update is going through? 20:07:47 we just unfroze this morning. 20:08:01 I need to check with ryanlerch on it 20:08:22 weird, the latest update on that ticket is.. it got reassigned from Paul Wouters to Paul Wouters :) 20:08:28 did he leave Red Hat? 20:09:08 seems like it 20:09:23 yes 20:10:30 * carlwgeorge contemplates how many people avoid leaving red hat to avoid losing all the logins tied to their red hat email 20:10:48 *laughs* 20:10:58 so the email address changing is a good sign, so many people just end up being non-responsive after leaving :p 20:11:42 So, hopefully by next week the change goes through ... and then we can work on the documentation and templates. Ya!! 20:11:49 whee! 20:12:02 would be happy to have something we can discuss at Dojo 20:12:16 (my presentation has one slide on EPEL Packagers0 20:12:23 When is the Dojo? 20:12:37 May 13/14 20:12:41 * carlwgeorge just notices rover now lets you set your preferred email alias 20:12:54 https://wiki.centos.org/Events/Dojo/May2021 20:12:58 maybe I'll remember to join for that one... 20:13:13 I haven't attended any of the virtual conferences 20:13:33 fwiw the last one was pretty good 20:13:41 Yep, hopefully docs and templates by then. 20:14:18 rover? 20:14:28 Anything else for the SIG that needs discussing? 20:14:32 yeah, the FOSDEM-attached Dojo was great 20:14:51 not much; remember to use EPELPackagersSIG tracking bug :) 20:15:02 did the comaintainers can request branches thing get pushed? 20:15:12 dcavalca: I don't know why, but those two bugz have run together in my head softhsmvmtouch ... soft-touch 20:15:13 yes, a couple of months ago 20:15:32 but if they can't submit updates it's not that helpful (though I guess I can use my provenpackager bit for that) 20:16:34 Moving on to epel8-next 20:16:59 carlwgeorge: I know the freeze ended just this morning, but ... any progress 20:18:31 i have not worked on it in the last week, but like you said i'm unblocked by the freeze now so hopefully i can make progress this week 20:19:25 OK, so we'll see how things progress this next week. 20:19:43 Anything else on -next before we move on? 20:19:59 nope 20:20:36 EPEL Fails-To-Install ... I haven't done anything with this last week. 20:21:05 I'm starting to see some daylight in my schedule, so I'm hoping the beginning of next week I can make some testing progress. 20:21:31 #topic EPEL-7 20:22:03 I didn't see anything for EPEL7 this week. Did anyone else? 20:22:50 #topic EPEL-8 20:23:33 I can see everyone is waiting with eager tension for the Open Floor ... but anything for EPEL8? 20:23:57 not hear, moving on... ;) 20:23:58 a bit tangential, we're hoping to have EPEL8 available for building Hyperscale packages against 20:24:06 but it needs to be discussed in centos-devel first 20:24:07 I finally caught up on some packaging work last weekend and got some epel8 builds pushed out. 20:24:11 ah, I was going to bring that up for open floor 20:24:18 (ansible-collections and a few misc python things) 20:24:19 I just posted to centos-devel: https://lists.centos.org/pipermail/centos-devel/2021-April/076793.html 20:24:22 ah, yeah let's wait for that 20:24:52 nirik: Ya!! I heard a couple people asking for the ansible stuff. 20:25:02 #topic General Issues / Open Floor 20:25:21 michel_slm: Please continue 20:25:22 epel got a shout out in the centos stream summit talk, which was nice 20:25:44 carlwgeorge: ooh, link? 20:25:51 wait, did I miss RH Summit 20:25:56 oh, and I split out ansible-test in the 2.9.x ansible 'classic' package to try and match the ansible.com and red hat engine builds. 20:26:16 I heard that ... now I feel bad. I watched the first 10 minutes, realized I'd heard everything at least three times and turned it off. 20:26:35 michel_slm: Yep ... or at least the April edition 20:27:06 it was this talk https://events.summit.redhat.com/widget/redhat/sum21/sessioncatalog/session/161223156919800114VW 20:27:17 but i don't think there is an on-demand option 20:27:47 oh wait yes here is the on-demand link https://events.summit.redhat.com/widget/redhat/sum21/sessioncatalog/session/1612985596209001PwQJ 20:27:50 Yes, there is an "on demand" button on that page. 20:27:56 thanks! 20:28:01 Sorry, not button, but a very small text link. 20:28:13 yeah that's why i missed it at first 20:28:13 I am registered, just that between Fedora 34 and forgetting to put it in my calendar, I totally forgot 20:28:43 the fingerprint login misconfig broke some people at work who eagerly upgraded on day 0 :p 20:31:42 those of us who upgraded on day -30, we suffered a bit too ;) 20:31:55 specially with gnome40 and extensions.... 20:32:00 If someone finds where in the on-demand they talk about EPEL, let me know 20:32:19 michel_slm: I think that's great that they are at least talking about making EPEL available for the SIG's. 20:32:55 Or was that dcavalca ... sorry, got you mixed up. 20:33:13 tdawson: we were both talking about it, no worries :) 20:33:30 tdawson: do feel free to weigh in on the thread in centos-devel if you'd like 20:34:46 Will do. Although I think it would be best if it was optional, or per SIG. Cuz I could see a SIG or two that don't want that. 20:35:03 oh yeah, the idea is definitely to make it optional 20:35:19 so I upgraded at the beginning of beta and apart from GNOME 40 design being a bit in flux, missed most of the excitement 20:35:22 like iptables not being upgradeable :p 20:35:59 tdawson: yeah, agreed. technically limiting this could be tricky as I hear it's basically just at the network level right now 20:36:26 I'm worried about the epel rebuilds that have already been done in cbs 20:36:37 that will screw up koji with the hash changes 20:36:44 at least until the next rebuild 20:37:24 pgreco: fwiw, in hyperscale we use a custom disttag to avoid that 20:37:31 also so we can tell apart our packages 20:37:52 yeah, thats the only issue I see... mismatches btween epel and things built/shipped in cbs 20:38:17 dcavalca: I'm talking about the other groups, I don't know which disttag they use, and if it will overlap with epel 20:38:29 yeah that's fair 20:38:37 but that's fixable by an update 20:40:03 tdawson: it's at 29:28 20:40:06 `this-is-the-real-epel` 20:40:09 Well, if you do inheritance right, so that EPEL is farther down the tree, I would think it wouldn't matter. The SIG package should win out. So if the SIG wanted to change to the EPEL package, they would just untag that. 20:40:37 yeah that would be the ideal outcome 20:40:57 Anyway, ya, I'll give my feedback on the email. 20:41:12 thanks! 20:41:21 carlwgeorge: Thanks. :) 20:41:26 * nirik nods 20:41:56 Anything else to talk about this week? 20:42:17 I'll bubble up https://github.com/fedora-eln/eln/issues/45 as we'd discussed about this in previous epel meetings 20:42:28 oh yeah 20:42:29 though it's not really relevant/related to epel anymore 20:42:58 kind of related, as I could see this will make the issue of "how to bootstrap a new EPEL branch" easier to solve 20:43:35 yeah, I can see this being leveraged down the road for some epel stuff, but I also agree with tdawson's comments in the ticket that it's best to keep it decoupled for the time being 20:43:36 Wow ... did I just head "make EPEL a first class participant in the ecosystem" 20:43:54 if we could start by collating what are the "leaf" EPEL packages we really, really care about and add them to this workload, what EPEL Packagers need to make sure is available is just "look at what dependencies get pulled in by this workload" 20:44:54 yup. EPEL can be a downstream user but let's not emphasize that for now, in case people object. if there's a new workload and we can easily add packages, and the packages just happen to be the ones we care about in EPEL, then... bonus 20:45:24 yup, I think that's the best course of action 20:45:29 I'd suggest: all those packages that aren't in rhel that are in epel8-build 20:45:34 in koji 20:45:49 Ya, sorry for being stern in that comment, I'm just really trying to keep EPEL and ELN Extras seperate, even though logically, one flows into the other. 20:46:33 nirik: that might be too many packages :) I think we want to keep it minimal 20:46:52 I think it's more that we'll need to attach a name to these packages 20:46:54 well, I doubt it's that many... most of them will be in rhel/eln base or whatever 20:47:05 and I doubt a single individual wants to sign up to own all the packages 20:47:13 but if the number is manageable, surewhynot 20:47:32 agreed with Miro, I don't think tdawson sounded harsh at all 20:47:34 fedpkg-minimal being the obvious one. 20:48:18 I could give you the number if you really want ... I haven't checked, but I currently know what packages are built in RHEL9, and what are released ... simple subtraction. 20:48:52 And you know what's soo coool with RHEL9 vs RHEL8 ... is that in a few weeks, ya'll will have that info as well. Ya!! 20:49:21 weeks/months ... sometime 20:50:15 developing in the open, so refreshing 20:50:39 Sorry, I'm really excited about RHEL9 / CentOS Stream 9 ... not necessily for the technical progress, but for the open-ness. 20:51:41 But, I diverge :) and I'm the one usually tasked with keeping us on task ... 20:51:51 Anything else EPEL related? 20:52:08 what's happening with 9 was jim's sales pitch to hire me (not this retroactive mess with 8) 20:52:43 carlwgeorge: And you've been stuck mainly with 8 haven't you. :( 20:53:46 Don't need to answer that. 20:54:00 Anyway, time is getting short, anything else before we close the meeting? 20:54:01 * carlwgeorge laugh/cries 20:55:05 Thank you all for comming this week, and for the good discussions. 20:55:12 Talk to you all next week. 20:55:19 thanks tdawson 20:55:26 thanks tdawson 20:55:30 #endmeeting