20:00:04 #startmeeting EPEL (2021-10-20) 20:00:04 Meeting started Wed Oct 20 20:00:04 2021 UTC. 20:00:04 This meeting is logged and archived in a public location. 20:00:04 The chair is tdawson. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 20:00:04 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:00:04 The meeting name has been set to 'epel_(2021-10-20)' 20:00:04 #meetingname epel 20:00:04 #chair nirik tdawson bstinson pgreco carlwgeorge michel dcavalca 20:00:04 #topic aloha 20:00:04 The meeting name has been set to 'epel' 20:00:04 Current chairs: bstinson carlwgeorge dcavalca michel nirik pgreco tdawson 20:00:13 .hi 20:00:14 carlwgeorge: carlwgeorge 'Carl George' 20:00:16 .hi 20:00:17 morning 20:00:20 dcavalca: dcavalca 'Davide Cavalca' 20:00:25 Hi carlwgeorge 20:00:31 .hello robert 20:00:32 rsc: robert 'Robert Scheck' 20:00:32 Hi dcavalca 20:00:35 Hi nirik 20:00:41 Hi rsc 20:01:05 hello! 20:01:07 .hi 20:01:08 pgreco: pgreco 'Pablo Sebastian Greco' 20:01:24 Hi pgreco 20:02:21 Wow ... we have pretty much everyone in the first minute ... should I start early or is everyone expecting the usual 5 minute wait? 20:03:14 #topic Old Business 20:03:24 .hi 20:03:25 themayor: Sorry, but user 'themayor' does not exist 20:03:30 hello 20:03:32 Hi themayor 20:03:35 Hi smooge 20:03:37 Wooops I never did that. Anyway I’m here 20:03:52 Jack, zodbot doesn't want you... :P 20:03:59 hey are you implying smooge and themayor are old business? Or is that cooincidence? :) 20:04:07 haha 20:04:18 Totally coincidence ... ya ... :) 20:04:29 yeah, let's go with coincidence.... 20:05:05 for me its a fair cop guv 20:05:17 Let's start with epel-next. carlwgeorge nirik ... and progress this week. 20:06:02 I don't think much this week? there's a pr pending, but might be after freeze. 20:06:11 Is that for bodhi? 20:06:43 or fedpkg ? 20:06:59 https://pagure.io/fedora-infra/ansible/pull-request/826 20:07:10 fedpkg pr was merged, but not released yet 20:07:11 koji sync listener (the thing that adds new packages to koji) 20:07:18 https://pagure.io/fedpkg/pull-request/453 20:07:37 I guess it has +1s to go in now... 20:07:56 dewit.gif 20:07:58 * nirik can push it 20:08:53 carlwgeorge: can you rebase? it doesn't want to rebase for me. ;( 20:09:05 sure 20:09:41 so, slow but steady progress. 20:09:54 rebased 20:10:08 I forgot to work on epel-macros ... is that work still needed? 20:10:23 yes but there is no rush 20:11:18 I'll leave it on my to-do list then. 20:11:28 Get to it when I can. 20:11:34 i think i said i was going to get the branch requested, so all you need to do is a pr to the epel9-next branch 20:11:48 Yep 20:12:17 I think the hard part will be going through the various macros, see what is needed and what isn't, that sort of thing. 20:12:46 yup 20:12:54 Although I know the answer to the following question, I'm going to ask it anyway so others know. How is the s390x situation progressing? 20:12:59 looks like i already got the branch https://pagure.io/releng/fedora-scm-requests/issue/37244 20:13:26 just pushed the epel8 commits to the epel9-next branch, so it's ready for whoever to set up a pr to update it as needed 20:13:28 tdawson: no progress that I know of. ;( 20:14:53 nirik Ya ... sad face here. I'm not quite sure where to apply pressure ... but I'm starting to try pushing around internally, see if we can get some movement. 20:15:09 feel free to do so. :) 20:16:13 Anything else for epel-next ? 20:16:14 tdawson: does it make sense to apply the pressure where "EPEL getting a first class citizen" was promised? 20:16:30 tdawson: i.e. mmcgrath? 20:16:51 rsc: that's who the pressure is rolling up to, yes 20:17:27 rsc: That will be my last point of pressure. Basically find the right places with warnings that pressure will come from the top if things don't start happening. 20:18:51 I don't want to play that card too many times. I'd like to keep Mike answering my emails. :) 20:19:21 :) 20:19:32 tdawson: I've no idea about the hierarchies, I would have assumed resources come from where the goal is promised. 20:20:06 So, do what's right simply. 20:20:19 no, mike isn't working on this himself 20:22:17 Yep ... anyway, we're hoping to get the s390x stuff done in a timely manner ... and I'll quit deleting what I'm about to say and just move on. :) 20:23:38 Next I have "Will It" particularly "Will It Install" working finally - https://tdawson.fedorapeople.org/epel/willit/status-overall.html 20:24:34 dnf have a bit of a leak with file holds, and a bit of memory. So the initial code was fairly easy, it was getting it not to barf when it ramped up to over 1000 packages it was looking at that was hard. 20:25:24 This week I'm hoping to have some "Will It Build" in place, as well as put in a proper git repo. 20:25:38 oh... shiny! 20:26:07 Right now it's here - https://github.com/tdawson/tdawson-misc-scripts/tree/master/willit 20:27:20 It's not to the "create bugzilla tickets" phase yet ... but that will be the goal. 20:27:52 Any questions before I move on? 20:27:53 hum... are the epel8 results right? 20:28:11 144 packages that don't install? 20:28:40 yeah, seems high, but ick 20:29:03 Alot of them are python packages ... and of those, it looks like there are just a handful of missing deps. 20:29:31 Actually ... hmm ... I wonder if it's not dealing with modules ... ugg ... 20:29:43 thats what I wondered, but I don't think thats the case 20:30:09 I'll double check. Shouldn't be too hard to determine. 20:30:43 Yesterday was the first day I was able to complete epel8 due to the dnf file-leak problem. I was just excited it finished, didn't give it a sanity check. 20:31:24 So, yep. I'll put that top on the list. Give it a sanity check. 20:31:50 I think it's right, there's a bunch of things that seem like they might just need rebuilds. 20:32:13 quite possible. 20:32:27 i'll take a closer look at the list and see if there is anything that i can rebuild to fix 20:32:39 OK, thanks. 20:32:52 i just gave negative karma to the one in epel8-testing to stop it from getting promoted 20:33:04 +1 20:34:19 *laughs as we sees the missing dependency* Can't stop the slop 20:34:54 Sorry ... I'm going to move on. 20:35:06 pgreco: Any progress on the macros ? 20:35:10 it would be nice if bodhi had an automatic "will it install" check that would block time based promotion 20:35:24 tdawson: not much time to test it, but I have everything ready to go 20:35:36 I'm trying to track down the user who asked for it 20:35:51 so we can test in a real life package 20:35:53 carlwgeorge: we could perhaps get something like that for ci... but I don't think ci runs on epel yet/currently? 20:36:04 pgreco: Sounds good. Hopefully they have some good examples. 20:36:27 yeah, user bkircher in case anybody knows him/her 20:37:43 I think that's it for old business 20:38:00 #topic EPEL-7 20:38:20 Anything new for epel7? 20:39:11 #topic EPEL-8 20:39:33 Aside from the packages that probrubly need a rebuild, anything new? 20:40:32 Oh, and if anyone is going through that list, the plasma-nm-* packages already have bugzilla's and their fix is in epel8-next. 20:41:22 #topic EPEL-Packaging-SIG 20:42:00 dcavalca: Anything for the Packaging-SIG ? 20:42:15 tdawson: nothing on my side 20:42:34 OK, that brings us to ... 20:42:40 #topic General Issues / Open Floor 20:43:21 should we start including an epel9 topic? 20:43:41 * nirik had a epel9 thing. ;) 20:43:45 We could. I haven't cuz that seems to be what the epel-next is. 20:43:55 that would be an ideal spot for status updates on the availability of epel9-next 20:44:15 That's a good idea ..., ok, I'll put it on the agenda ... 20:44:22 #topic EPEL-9 20:44:25 .releng 10339 20:44:26 nirik: Issue #10339: Create empty `/epel/9` structure - releng - Pagure.io - https://pagure.io/releng/issue/10339 20:44:27 also i just wanted to point out we have an epel9 version in bugzilla now, so some requests are coming in for epel9 packages https://bugzilla.redhat.com/buglist.cgi?product=Fedora%20EPEL&version=epel9 20:44:44 yeah, I feared that would happen 20:45:07 i don't think it's an issue to have the bugs exist, good to see the interest early 20:45:11 this seems a good thing to me 20:45:23 most of them have "once available" in the subject 20:45:33 expectations are correctly set :) 20:46:02 I suppose, but it's another open bug lingering around... 20:47:13 Ohh ... there is one for epel-rpm-macros ... I'll be looking at that while I work on it. 20:47:37 the chromium one was the wrong version, it was an epel8 report 20:48:23 anyhow, re: the releng issue... shall we hold off on making a /epel/9 on mirrors? or is that something people want us to do now? 20:48:32 on nirik's issue, i think it's fair to say no this far out. it's ok for /epel/next/9/ because we're close enough to that being ready 20:49:08 I see no harm either way, but if we do create we should write up expectations somewhere 20:49:22 so folks don't get needlessly confused 20:49:22 I have mixed feelings. It would be nice to have it for scripts ... but on the other hand ... it seems very early, and people might start looking for RHEL9 to go along with their epel9 directory. 20:49:37 i feel like the reporter failed to explain why it matters 20:49:38 yeah 20:49:44 personally, the sooner I have it the sooner I can setup my internal mirroring stuff and drop special casing for c9s :) 20:49:57 but it's not really a big deal 20:49:57 we could ask them to expand on why they want it... 20:50:25 doesn't seem worth it if we're just gonna say no anyways, that was just an open ended thought i had 20:51:46 ok, proposed: close for now and tell them we will make it when epel9 is closer to really existing. 20:52:33 +1 20:52:59 i think they are doing the same thing that dcavalca does.. copy all the code, rebuild it all in their own build system, run through ci, then feed back to us. With the directories missing they are running into the same issue dcavalca mentioned of having to special case their scripts 20:53:37 we actually don't rebuild anything, just import the repos and snapshot them 20:53:59 ok I thought facebook did their own complete rebuild of stuff. 20:53:59 so yeah, for c9s right now I have some special casing to tell it to skip epel9 20:54:50 that said, I am ok with the proposal 20:54:55 smooge: nooope, I'm actually trying to minimize rebuilds as much as possible and getting most of them upstreamed where we can 20:55:26 and fwiw, the 20:55:35 the epel packagers sig has made this a lot easier 20:55:56 as I can just get something packaged there instead of having to maintain an internal fork that will inevitably get stale :) 20:58:05 Did we get a final tally? 20:58:36 I'm ok with nirik's proposal 20:58:44 well no one voted against it. 20:59:13 Yep. So, nirik sounds like we tell them no for now. 20:59:15 carlwgeorge, are you for it or against it 20:59:40 ok, I can close the ticket in a bit, unless someone else wants to... 20:59:55 We'll let you be the bad guy. :) 21:00:22 And, looks like our time is up. 21:00:32 for or against the request, or for or against telling them no 21:00:46 i think we should say no for now 21:00:57 Thank you everyone for coming and participating. It's been a good meeting and discussions. 21:01:04 thanks tdawson 21:01:07 I'll talk to ya'll next week. 21:01:11 thanks tdawson 21:01:16 #endmeeting