On Wed, Mar 8, 2023 at 9:43 AM Troy Dawson <tdawson@xxxxxxxxxx> wrote: > > > > On Wed, Mar 8, 2023 at 6:31 AM Troy Dawson <tdawson@xxxxxxxxxx> wrote: >> >> On Tue, Mar 7, 2023 at 7:16 PM Carl George <carl@xxxxxxxxxx> wrote: >>> >>> On Tue, Mar 7, 2023 at 2:18 PM Troy Dawson <tdawson@xxxxxxxxxx> wrote >>> > >>> > RHEL has been very good (lately) about their NVR's being higher than EPEL's. >>> > If that is so, the EPEL packages don't take precedence over RHEL's. >>> >>> They may not when you first check. The risk in leaving the branch >>> active is that a maintainer may bump the version and/or release and >>> start overriding the RHEL package at any given time. We don't >>> currently have a mechanism to freeze the distgit branch but leave the >>> package in the repo. Our current calculus is "if the package is in >>> RHEL, it needs to be promptly retired from EPEL". Leaving packages >>> longer means that someone needs to continually check that the >>> duplicating packages haven't started overriding their RHEL equivalent. >> >> >> Before I dig through all my emails, let me ask if you have got any examples of EPEL packagers updating a package after RHEL has released it? >> (Within a reasonable time frame, which is to say a month after the release) The most recent example I remember is python-sqlalchemy. It was available in EPEL 9 at version 1.4.37. That same version was added to CentOS Stream 9 in preparation to go into RHEL 9.1. The EPEL maintainer didn't notice the retirement warning bug and continued to update the package to newer versions in EPEL 9. It made it up to version 1.4.44 before it was retired. That last update to 1.4.44 was pushed to stable on 2022-11-23, eight days after the RHEL 9.1 release. Anyone that had it installed previously won't get upgraded to the RHEL 9.1 package which is still at version 1.4.37. Thankfully the RHEL maintainer agreed to rebase it in RHEL 9.2 to eventually resolve the upgrade path. https://bugzilla.redhat.com/show_bug.cgi?id=2098498 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-cee8cb8dc1 https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx/thread/KGKSCFABQE6MJ5F4RKR3HUXW73GGTSU6/ https://bugzilla.redhat.com/show_bug.cgi?id=2152649 It's happened before, and I'd like to minimize the window where it can happen again in the future. I understand wanting to be courteous to rebuild users, but we need to find the right balance. > > > I'm sorry, it's sounding like I'm trying to argue with you, and I'm not. > I just have no idea why you feel packagers updating after RHEL has released a package is a problem. It's not just updating after RHEL, it's updating the package to a higher NVR than what RHEL plans to release, as we saw in the sqlalchemy example. > Back before we started doing this EPEL2RHEL, we did have a problem, and that was because many packagers had no idea that their package was in RHEL. > Since we started EPEL2RHEL we've had the opposite problem. They get so excited about not having to maintain the package that they drop it too soon. > If I've missed things, please let me know. Because I feel like I'm not seeing a problem that you are seeing. > >> >> Beyond the reasoning about timing, here's my other problem. >> In the script I'm writing, I can't check if a package has been released by RHEL, I can only check if a package has been released by Alma and/or Rocky. >> It's the same reason that willit is only checking against Alma. >> The whole subscription problem. >> >> Troy >> > _______________________________________________ > epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- Carl George _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
