2024-06-26 18:00:09 <@tdawson:fedora.im> !startmeeting EPEL (2024-06-26)
2024-06-26 18:00:10 <@meetbot:fedora.im> Meeting started at 2024-06-26 18:00:09 UTC
2024-06-26 18:00:10 <@meetbot:fedora.im> The Meeting name is 'EPEL (2024-06-26)'
2024-06-26 18:00:17 <@tdawson:fedora.im> !meetingname epel
2024-06-26 18:00:18 <@meetbot:fedora.im> The Meeting Name is now epel
2024-06-26 18:00:22 <@tdawson:fedora.im> !topic aloha
2024-06-26 18:00:43 <@yselkowitz:fedora.im> !hi
2024-06-26 18:00:43 <@zodbot:fedora.im> Yaakov Selkowitz (yselkowitz)
2024-06-26 18:00:44 <@nirik:matrix.scrye.com> morning
2024-06-26 18:00:48 <@rcallicotte:fedora.im> !hi
2024-06-26 18:00:50 <@zodbot:fedora.im> Robby Callicotte (rcallicotte) - he / him / his
2024-06-26 18:00:54 <@jrichardson:matrix.org> !hi
2024-06-26 18:00:56 <@zodbot:fedora.im> James Richardson (jrichardson)
2024-06-26 18:01:01 <@rcallicotte:fedora.im> I'm here but fighting fires :(
2024-06-26 18:01:19 <@tdawson:fedora.im> Hi yselkowitz Robby Callicotte and James Richardson 
2024-06-26 18:01:22 <@nhanlon:beeper.com> !hi
2024-06-26 18:01:23 <@zodbot:fedora.im> Neil Hanlon (neil) - he / him / his
2024-06-26 18:01:24 <@tdawson:fedora.im> Morning nirik 
2024-06-26 18:01:36 <@carlwgeorge:matrix.org> !hi
2024-06-26 18:01:39 <@zodbot:fedora.im> Carl George (carlwgeorge) - he / him / his
2024-06-26 18:01:42 <@tdawson:fedora.im> Hi Neil Hanlon and Carl George 
2024-06-26 18:01:47 <@nhanlon:beeper.com> heya folks
2024-06-26 18:02:15 <@tdawson:fedora.im> Robby Callicotte: Those fires need to be fought.  But we're glad you are at least partly here.
2024-06-26 18:03:20 <@nhanlon:beeper.com> 🪣 🌊
2024-06-26 18:03:39 <@salimma:fedora.im> !hi
2024-06-26 18:03:40 <@zodbot:fedora.im> Michel Lind (salimma) - he / him / his
2024-06-26 18:03:51 <@tdawson:fedora.im> Hi Michel Lind 🎩 
2024-06-26 18:04:14 <@dherrera:fedora.im> !hi
2024-06-26 18:04:14 <@smooge:fedora.im> hello
2024-06-26 18:04:15 <@zodbot:fedora.im> Diego Herrera (dherrera) - he / him / his
2024-06-26 18:04:26 <@tdawson:fedora.im> Hi Diego Herrera 
2024-06-26 18:04:33 <@tdawson:fedora.im> Hello Stephen J Smoogen 
2024-06-26 18:05:23 <@tdawson:fedora.im> !topic End Of Life (EOL)
2024-06-26 18:05:29 <@tdawson:fedora.im> CentOS Stream 8 / epel-8-next went EOL on 2024-05-31
2024-06-26 18:05:29 <@tdawson:fedora.im> https://endoflife.date/rhel
2024-06-26 18:05:29 <@tdawson:fedora.im> CentOS Stream 9 / epel-9-next goes EOL in 2027-05-31
2024-06-26 18:05:29 <@tdawson:fedora.im> https://endoflife.date/centos-stream
2024-06-26 18:05:29 <@tdawson:fedora.im> RHEL 7 / epel-7 will go EOL on 2024-06-30
2024-06-26 18:05:42 <@tdawson:fedora.im> So next week is the end of epel7
2024-06-26 18:05:57 <@nirik:matrix.scrye.com> ⌛
2024-06-26 18:06:04 <@tdawson:fedora.im> Do we have everything in place?   Or tickets created?  
2024-06-26 18:06:21 <@salimma:fedora.im> related: tickets filed against epel 7 will auto-close right?
2024-06-26 18:06:26 <@nirik:matrix.scrye.com> I was going to bring up this and epel8-next eol...
2024-06-26 18:06:32 <@carlwgeorge:matrix.org> we can probably take the cs8/epel8-next eol reminder out of that text since it has already passed
2024-06-26 18:07:03 <@nirik:matrix.scrye.com> it might be nice to have a SOP for eol epel releases and spell out what you want releng to do and what others want to do and such
2024-06-26 18:07:48 <@tdawson:fedora.im> So have it in the epel documentation?
2024-06-26 18:07:55 <@carlwgeorge:matrix.org> indeed, and to spell out what happens differently for epel next.  we're going through the first ever eol for one of those.  https://pagure.io/releng/issue/12147
2024-06-26 18:08:17 <@nirik:matrix.scrye.com> sure, either in epel or releng, I don't care as long as it's somewhere we can find it. ;)
2024-06-26 18:08:24 <@carlwgeorge:matrix.org> then again, we're only ever going to do it once more for epel9-next, so maybe not worth making a full sop for that part
2024-06-26 18:08:38 <@carlwgeorge:matrix.org> !link https://pagure.io/releng/issue/12147
2024-06-26 18:08:42 <@nirik:matrix.scrye.com> yeah, next is less important...
2024-06-26 18:09:04 <@tdawson:fedora.im> If we did it in the releng documentation, where would be the place for that?
2024-06-26 18:09:14 <@nirik:matrix.scrye.com> but for example, for epel7, do we want to try and ping all open bugzilla bugs telling people it's about to eol and then close them EOL after? (which is what we do for fedora)
2024-06-26 18:09:39 <@carlwgeorge:matrix.org> i'm all in favor of doing things like fedora whenever possible
2024-06-26 18:09:56 <@smooge:fedora.im> In this case, I would probably say it is a little late to ping people
2024-06-26 18:09:57 <@tdawson:fedora.im> Oh, that's much nicer than I was thinking for the bugs.  I was just thinking of closing them all.
2024-06-26 18:10:00 <@nirik:matrix.scrye.com> in here: https://docs.fedoraproject.org/en-US/infra/releng_misc_guide/ or possibly in https://docs.fedoraproject.org/en-US/infra/release_guide/release_eol/
2024-06-26 18:10:09 <@salimma:fedora.im> true, I guess for Fedora we ping them
2024-06-26 18:10:34 <@yselkowitz:fedora.im> there is a much bigger gap between epel versions than there are fedora versions, bugs are more likely to be no longer applicable to the next epel
2024-06-26 18:10:44 <@nirik:matrix.scrye.com> note: someone would need to actually do this work. ;) (not it!)
2024-06-26 18:10:54 <@smooge:fedora.im> I was thinking that at this point it is a 'close all EL-7' tickets time as a lot of the items are not going to work in EL-8 or beyond
2024-06-26 18:11:24 <@smooge:fedora.im> not it for doing the closing or not it for writing the instructions?
2024-06-26 18:11:47 <@smooge:fedora.im> I can write up the stuff for EPEL-7 if that is ok?
2024-06-26 18:11:56 <@tdawson:fedora.im> I'm ok doing the bugzilla closings.  But it will probrubly not happen until July 8th due to vacation and holidays.
2024-06-26 18:12:06 <@smooge:fedora.im> as an emeritus last act type thing
2024-06-26 18:12:36 <@smooge:fedora.im> 'i come here not to praise EPEL-7, but to bury it'
2024-06-26 18:12:49 <@nirik:matrix.scrye.com> note that there's scripts that are used in fedora... could be modified
2024-06-26 18:14:28 <@tdawson:fedora.im> Doing a batch bugzilla <anything>, isn't too hard.   But I wouldn't mind looking at Fedora's to make the wording as close as possible.
2024-06-26 18:14:52 <@salimma:fedora.im> I guess we can also help close our individual tickets unless Troy has an automated script
2024-06-26 18:15:09 <@salimma:fedora.im> but yeah might as well do it uniformly and avoid confusion
2024-06-26 18:15:12 <@smooge:fedora.im> I will post something to the list of potential wording?
2024-06-26 18:15:24 <@smooge:fedora.im> Do we have a ticket in the epel tracker for this?
2024-06-26 18:15:42 <@nirik:matrix.scrye.com> note that the fedora scripts close things EOL, which normal users cannot I don't think... might need privs to do that
2024-06-26 18:15:50 <@tdawson:fedora.im> Closing all the epel7 bugs?  Not that I've noticed.
2024-06-26 18:16:46 <@carlwgeorge:matrix.org> tangential question for the group related to retirements:  i think it would be worthwhile to have epel-release 8 obsolete epel-next-release 8.  any systems that still have epel-next-release installed, whether their os is eol or not, should stop checking for that repo, and we have an easy way to accomplish that with an obsoletes in the main epel-release package.  i haven't set up a pr for this yet, but can throw that up right after the meeting.  any concerns?
2024-06-26 18:17:15 <@tdawson:fedora.im> Oh ... ok.  I'll have to check and see if I can do an EOL.  But ... I'll wait till next week to check.
2024-06-26 18:17:47 <@tdawson:fedora.im> Carl George: So, even if they are still running CentOS Stream 8, it will just stop them from checking the epel8-next repo ... correct?
2024-06-26 18:18:27 <@carlwgeorge:matrix.org> yup.  or if they happen to have epel-next-release installed on rhel8 or similar, which definitely happens even if it isn't recommended.
2024-06-26 18:19:04 <@tdawson:fedora.im> I don't see any problems with that.
2024-06-26 18:19:21 <@nirik:matrix.scrye.com> not sure it's worth the trouble, but sure... ;)
2024-06-26 18:20:10 <@tdawson:fedora.im> Is there already a releng ticket for archiving (and other stuff) for epel7 ?
2024-06-26 18:20:32 <@tdawson:fedora.im> Or will that happen the day it goes EOL?
2024-06-26 18:21:12 <@carlwgeorge:matrix.org> i can file one similar to the epel8-next one for eol, and yeah i think on eol day is the right time for that
2024-06-26 18:21:31 <@carlwgeorge:matrix.org> on that day i can yank the epel7 build targets in koji to kick things off
2024-06-26 18:21:45 <@nirik:matrix.scrye.com> +1
2024-06-26 18:21:45 <@carlwgeorge:matrix.org> or maybe the day after to be safe
2024-06-26 18:22:27 <@carlwgeorge:matrix.org> did we happen to have an issue for epel6 retirement?
2024-06-26 18:22:44 <@nirik:matrix.scrye.com> cannot recall.
2024-06-26 18:23:34 <@carlwgeorge:matrix.org> if anyone happens to run across that, i'd love to bookmark it, and i'm sure Stephen J Smoogen would fine it useful for what he's writing up for epel7 retirement as well
2024-06-26 18:23:45 <@carlwgeorge:matrix.org> if anyone happens to run across that (if it exists), i'd love to bookmark it, and i'm sure Stephen J Smoogen would fine it useful for what he's writing up for epel7 retirement as well
2024-06-26 18:23:59 <@smooge:fedora.im> we did not have an issue for EPEL-6 because I don't think we had this repo when that happened
2024-06-26 18:24:15 <@tdawson:fedora.im> So, this is the tasks I have (along with who is doing them)
2024-06-26 18:24:23 <@tdawson:fedora.im> - have epel8-release obsolete epel8-next - carl
2024-06-26 18:24:23 <@tdawson:fedora.im> - Close bugzillas  - tdawson
2024-06-26 18:24:23 <@tdawson:fedora.im> - Write-up SOP - Smooge
2024-06-26 18:24:23 <@tdawson:fedora.im> - File releng issue to EOL epel7 - carl
2024-06-26 18:24:23 <@carlwgeorge:matrix.org> there are epel6 issues in there, but nothing i see for retirement
2024-06-26 18:25:41 <@tdawson:fedora.im> This is exciting.  I know we've EOLed epel releases before, but epel7 is rather huge in terms of people using it.
2024-06-26 18:26:09 <@tdawson:fedora.im> Anything else before I move on to the next topic?
2024-06-26 18:26:38 <@tdawson:fedora.im> !topic EPEL Issues https://pagure.io/epel/issues
2024-06-26 18:26:43 <@tdawson:fedora.im> https://pagure.io/epel/issues?tags=meeting&status=Open
2024-06-26 18:26:55 <@tdawson:fedora.im> We don't have any open issues this week.
2024-06-26 18:27:37 <@tdawson:fedora.im> Next week we'll probrubly be talking about "catch", but that can wait for next week.
2024-06-26 18:27:49 <@carlwgeorge:matrix.org> small follow up, https://pagure.io/epel/issue/278 is closed/approved but the implementation isn't done yet.  i need to follow up with adrian.
2024-06-26 18:28:05 <@carlwgeorge:matrix.org> implementation being over in https://pagure.io/fedora-infrastructure/issue/11968
2024-06-26 18:28:28 <@carlwgeorge:matrix.org> but good news, the 8.8 test worked as expected
2024-06-26 18:28:53 <@tdawson:fedora.im> cool
2024-06-26 18:29:16 <@tdawson:fedora.im> Thanks for keeping us informed, as well as thanks to those working on it.
2024-06-26 18:29:32 <@tdawson:fedora.im> !topic Old Business
2024-06-26 18:29:49 <@tdawson:fedora.im> do we have any old business?  Other than the old business we've already covered?
2024-06-26 18:30:15 <@yselkowitz:fedora.im> any updates on epel 10?
2024-06-26 18:30:26 <@tdawson:fedora.im> I was about to ask about that.
2024-06-26 18:30:43 <@tdawson:fedora.im> Let me give an update on the 10 mass rebuild. 
2024-06-26 18:31:16 <@tdawson:fedora.im> It's done, and packages are making their way through gating.  As a result ... right now composes are failling, but that's sorta expected.
2024-06-26 18:31:50 <@tdawson:fedora.im> I'm hoping that by next week enough of the packages have made it through the gating that composes are back to normal.
2024-06-26 18:32:52 <@jonathanspw:fedora.im> !hi
2024-06-26 18:32:53 <@zodbot:fedora.im> Jonathan Wright (jonathanspw)
2024-06-26 18:32:54 <@tdawson:fedora.im> How that affects epel10 plans ... I'm not positive.
2024-06-26 18:32:59 <@tdawson:fedora.im> Hi Jonathan Wright 
2024-06-26 18:33:07 <@jonathanspw:fedora.im> Sorry I'm late, distracted by contractor here installing 2g fiber at my house :)
2024-06-26 18:33:13 <@jonathanspw:fedora.im> finally joining the modern world...
2024-06-26 18:33:19 <@salimma:fedora.im> 2g !
2024-06-26 18:33:32 <@jonathanspw:fedora.im> They assure me 8g is coming this year.
2024-06-26 18:33:34 <@carlwgeorge:matrix.org> humble brag lol
2024-06-26 18:33:35 <@tdawson:fedora.im> making me jealous.  ;)
2024-06-26 18:33:58 <@rcallicotte:fedora.im> Jealous... I'm still on carrier pigeon... lol
2024-06-26 18:34:53 <@tdawson:fedora.im> I've been assured that any type of fiber is coming to a house near me*  soon**  (* 15 miles away  ** next few years)
2024-06-26 18:35:00 <@salimma:fedora.im> I remember when 2.5G was fast. for mobile...
2024-06-26 18:35:23 <@salimma:fedora.im> AT&T has been promising to lay fiber to my village for years. when I moved here I was so excited when I tried to signup and it says 5 for the bandwith
2024-06-26 18:35:32 <@salimma:fedora.im> then I realized it's 5... Mbps. no wonder it felt a bit cheap
2024-06-26 18:35:58 <@carlwgeorge:matrix.org> James Richardson switched the batcave sync for c10 from composes to mirrored content, and also added epel10.0 tags to robosignatory
2024-06-26 18:36:04 <@jonathanspw:fedora.im> I'm getting 2g for $99/mo
2024-06-26 18:36:15 <@jonathanspw:fedora.im> it's from windstream
2024-06-26 18:36:30 <@carlwgeorge:matrix.org> next up will be an attempt to verify the robosignatory stuff works in staging
2024-06-26 18:36:43 <@tdawson:fedora.im> Carl George: Very cool.
2024-06-26 18:36:59 <@tdawson:fedora.im> robosignatory is where the packages get signed after being built, correct?
2024-06-26 18:37:11 <@carlwgeorge:matrix.org> correct, and does some tag shuffling
2024-06-26 18:37:56 <@carlwgeorge:matrix.org> my basic understanding is it watches for builds to get the incoming tag, then signs them, then tags them with the outgoing tag and removes the incoming tag
2024-06-26 18:38:05 <@nirik:matrix.scrye.com> it should be pretty easy to test that in prod too (well, easier if you don't want to wait for me to have time to look at staging)
2024-06-26 18:38:12 <@tdawson:fedora.im> Cool.
2024-06-26 18:38:33 <@carlwgeorge:matrix.org> hehe, testing in prod is always fun
2024-06-26 18:38:44 <@carlwgeorge:matrix.org> https://pagure.io/fedora-infra/ansible/pull-request/2066#request_diff is the change
2024-06-26 18:39:24 <@tdawson:fedora.im> I think in a couple of weeks, things should have settled down from the mass rebuild, and maybe, we can start thinking about prod.
2024-06-26 18:40:00 <@carlwgeorge:matrix.org> testing that in prod will involve actually putting stuff in prod koji, which brings me to another question
2024-06-26 18:40:27 <@conan_kudo:matrix.org> !hi
2024-06-26 18:40:29 <@zodbot:fedora.im> Neal Gompa (ngompa) - he / him / his
2024-06-26 18:40:35 <@tdawson:fedora.im> Hi Conan Kudo 
2024-06-26 18:40:56 <@salimma:fedora.im> that's not bad. I pay $80 for 1 gbit
2024-06-26 18:41:06 <@carlwgeorge:matrix.org> the plan of record has been a soft launch as soon as we get all the pieces in place, with an official launch in november or december.  ideally i'd like the soft launch ready in time for the epel10 hackfest at flock.
2024-06-26 18:41:18 <@jonathanspw:fedora.im> currently paying $110 for "gigabit" (non-symmetrical) cable 1g/35m
2024-06-26 18:41:44 <@tdawson:fedora.im> That sounds good to me, if possible.
2024-06-26 18:41:52 <@salimma:fedora.im> the sooner the better, I plan to dogfood the refactored ebranch and ideally I can say at Flock that it definitely works :)
2024-06-26 18:42:23 <@carlwgeorge:matrix.org> while looking through the steps for bodhi, something occurred to me.  we could set up the epel10.0 bodhi release initially to work like rawhide, in that there is not testing repo and updates get autocreated for each build.  i think that would be a good initial setup for epel10 during the soft launch phase.
2024-06-26 18:42:37 <@nirik:matrix.scrye.com> should be doable. Just needs the koji setup and then bodhi config and syncing...
2024-06-26 18:42:41 <@jonathanspw:fedora.im> That would be really handy
2024-06-26 18:43:13 <@nirik:matrix.scrye.com> might be unexpected for people... otherwise should be fine
2024-06-26 18:43:21 <@carlwgeorge:matrix.org> it doesn't drastically reduce the amount of work needed, the main thing i think would be we don't have to wait for the fedpkg changes for minor version branch requests to land
2024-06-26 18:43:32 <@salimma:fedora.im> oh... yeah. and when there's a RHEL 10 beta that's when you enable gating but for the 10.0 repo
2024-06-26 18:43:46 <@salimma:fedora.im> we're distinguishing between 'epel10' and 'epel10.0' right?
2024-06-26 18:44:05 <@carlwgeorge:matrix.org> it varies depending on the scope
2024-06-26 18:44:08 <@tdawson:fedora.im> Ya, at some point we'll need to put it back the other way, but for starting, I really like the idea.
2024-06-26 18:44:35 <@carlwgeorge:matrix.org> initial setup would be:
2024-06-26 18:44:35 <@carlwgeorge:matrix.org> 
2024-06-26 18:44:35 <@carlwgeorge:matrix.org> epel10 branch -> epel10.0 build -> epel10.0 update -> epel10 repo path
2024-06-26 18:45:09 <@carlwgeorge:matrix.org> i'm thinking right before the official announcement in nov/dec is when we turn on the testing repo
2024-06-26 18:45:24 <@carlwgeorge:matrix.org> this will also really help the bootstrap effort i think, like at the flock hackfest
2024-06-26 18:46:02 <@yselkowitz:fedora.im> will make early epel 11 a lot easier too
2024-06-26 18:46:26 <@tdawson:fedora.im> Sorry, you lost me with the "epel10 branch -> epel10.0 build -> epel10.0 update -> epel10 repo path"  My brain isn't following.
2024-06-26 18:46:31 <@carlwgeorge:matrix.org> speaking of which, i did get approved for funding, so i'll be at my own hackfest after all
2024-06-26 18:46:37 <@salimma:fedora.im> we can sort out the details later, I suppose
2024-06-26 18:46:43 <@tdawson:fedora.im> Ya!!
2024-06-26 18:47:17 <@nirik:matrix.scrye.com> cool
2024-06-26 18:47:19 <@rcallicotte:fedora.im> YAY!!
2024-06-26 18:47:22 <@jonathanspw:fedora.im> y'all pray for me though
2024-06-26 18:47:24 <@smooge:fedora.im> congrats!
2024-06-26 18:47:42 <@jonathanspw:fedora.im> y'all pray for me though.  I get to listen to the freight train at night :p
2024-06-26 18:48:23 <@carlwgeorge:matrix.org> in dist-git, the branch name will be epel10, so that people running `fedpkg request-branch epel10` get what they expect.  when they create a build for that, it will land in an epel10.0 koji tag, and feed into an epel10.0 bodhi update.  the repo path will be epel/10 so that requests coming in don't need to determine the minor version (it's not in the c10 os-release file).
2024-06-26 18:48:46 <@tdawson:fedora.im> Ahhh .... ok.   Yes.
2024-06-26 18:48:59 <@tdawson:fedora.im> Thanks for explaining.
2024-06-26 18:49:07 <@carlwgeorge:matrix.org> sure thing
2024-06-26 18:49:35 <@jonathanspw:fedora.im> Will building against a specific target be possible or only `epel10`?
2024-06-26 18:50:19 <@carlwgeorge:matrix.org> yes, once the targets exist.  the initial rollout will only be `epel10` and `epel10.0` targets, going to the same tags.
2024-06-26 18:50:44 <@tdawson:fedora.im> For right now, I believe there can only be the one target.  But after RHEL is released, I believe you should be able to target ..... ya ... carl said it better. :)
2024-06-26 18:50:48 <@jonathanspw:fedora.im> perfect
2024-06-26 18:51:43 <@carlwgeorge:matrix.org> i'm going to start drafting an update to post in discourse and the mailing list to set expectations around the soft launch period, and ask maintainers to not start building immediately if they see the build targets, because that doesn't mean all the pieces are working yet.  we have eager maintainers that just start building when they notice stuff, as i learned with epel9-next.
2024-06-26 18:52:12 <@tdawson:fedora.im> We're getting a little short of time.  I'm going to switch to Open Floor, and if nobody has any open floor stuff, we can go back to epel10.
2024-06-26 18:52:23 <@tdawson:fedora.im> !topic General Issues / Open Floor
2024-06-26 18:52:34 <@tdawson:fedora.im> Does anyone have anything for Open Floor?
2024-06-26 18:53:10 <@carlwgeorge:matrix.org> i was gonna say all that epel10 stuff in the open floor, but it already came up, so i think i'm good
2024-06-26 18:53:27 <@jonathanspw:fedora.im> Will EPEL7 drop off on/near EOL date or is it getting pushed out 30 days or something like how centos 8 was when it hit EOL?
2024-06-26 18:54:02 <@jonathanspw:fedora.im> (I saw stuff about fedora specifically but it didn't mention epel)
2024-06-26 18:54:30 <@tdawson:fedora.im> I believe Carl is going to do start things the day of, or the day after
2024-06-26 18:54:41 <@carlwgeorge:matrix.org> i'm open to either way tbh
2024-06-26 18:54:42 <@tdawson:fedora.im> Starting with the target.
2024-06-26 18:54:54 <@carlwgeorge:matrix.org> yeah, day of or day after, yank the build target for sure
2024-06-26 18:55:06 <@nirik:matrix.scrye.com> depends on what you mean by drop off. ;)
2024-06-26 18:55:49 <@nirik:matrix.scrye.com> the archiving will be sometime soon after that... as far as usage drop off... who knows? ;)
2024-06-26 18:56:48 <@carlwgeorge:matrix.org> considering that mirrormanager is already set up to redirect eol epel versions to archive mirrors, perhaps we don't need a 30 day period like centos
2024-06-26 18:56:50 <@jonathanspw:fedora.im> I mean repos, sorry
2024-06-26 18:56:58 <@carlwgeorge:matrix.org> considering that mirrormanager is already set up to redirect eol epel major versions to archive mirrors, perhaps we don't need a 30 day period like centos
2024-06-26 18:57:53 <@tdawson:fedora.im> My vote is for the day after (for the target).  Someone is always going to say they thought it was at the very end of the day.  So you might as well do it the day after.
2024-06-26 18:58:57 <@carlwgeorge:matrix.org> centos doesn't do the archive redirect to vault, they force people to manually configure vault repos if they want them.  i think that's the reason for having a grace period for taking down the repos.
2024-06-26 18:59:24 <@jonathanspw:fedora.im> I didn't realize epel had an auto-redirect.  IMO it shouldn't.
2024-06-26 18:59:25 <@nirik:matrix.scrye.com> ok. I didn't know there was a grace period.
2024-06-26 19:00:14 <@tdawson:fedora.im> Hmm ... we didn't have a grace period for CentOS Stream 8.  It got yanked so fast some bits had to be put back for me to do the final release.
2024-06-26 19:00:22 <@nirik:matrix.scrye.com> fedora has always done it that way. Changing that is of course possible, but I don't think it would be very nice to do that for epel7 a few days before it eols
2024-06-26 19:00:47 <@jonathanspw:fedora.im> not worth messing with, wasn't implying we should try to change it.
2024-06-26 19:00:55 <@jonathanspw:fedora.im> not worth messing with, wasn't implying we should try to change it, at least not for 7
2024-06-26 19:01:27 <@nirik:matrix.scrye.com> yeah, a choice was made long ago to do that and now it's kinda expected. ;( But we could change it with enough noise...
2024-06-26 19:01:27 <@jonathanspw:fedora.im> I didn't realize Fedora did it.  I've never stayed on an EOL fedora release so never ran into it I guess.
2024-06-26 19:01:27 <@carlwgeorge:matrix.org> https://mirrors.fedoraproject.org/metalink?repo=epel-4&arch=x86_64 still works fwiw
2024-06-26 19:01:32 <@tdawson:fedora.im> Looks like our time is up.  Thank you all for coming and for the good disucssions.  And thank you all for all the work you do for EPEL and it's community.
2024-06-26 19:01:42 <@salimma:fedora.im> thanks Troy!
2024-06-26 19:01:49 <@jrichardson:matrix.org> thanks Troy!
2024-06-26 19:01:50 <@nirik:matrix.scrye.com> epel4! 🤘
2024-06-26 19:01:59 <@tdawson:fedora.im> I'll talk to ya'll next week, if not sooner.
2024-06-26 19:02:01 <@carlwgeorge:matrix.org> maybe the grace period thing was intentionally a centos linux thing, not stream
2024-06-26 19:02:17 <@tdawson:fedora.im> !endmeeting