I generally agree with this idea, and have suggested as such a few times over the course of planning EPEL 10. However, I haven't yet been able to write up a pull request to propose such changes to the EPEL updates policy. This would be needed for the EPEL Steering Committee to vote on the changes and make them official. If anyone wants to help write those up, I'd be happy to collaborate to sort out the ideal wording. Until, EPEL updates must follow the policy as it's currently written. If we did already have the EPEL updates policy in a place that it reflected RHEL minor version policies, this change would only be allowed on the epel10 (10.2) branch, and the epel10.1 branch would be restricted to security and bug-fix only. On Tue, Sep 2, 2025 at 8:50 PM Orion Poplawski <orion@xxxxxxxx> wrote: > > I'm the one who made the request. I do think it would be important to > update in order to support modern libmamba. I was hoping that the other > users of libyaml-cpp would chime in, but they have not yet done so. > > FWIW - RHEL has been pushing soname updates in RHEL point releases for > things in CRB and possibly appstream. So now that EPEL aligns with RHEL > point releases I think it would be reasonable to relax the incompatible > update policy in EPEL. > > Orion > > On 9/2/25 17:01, Carl George wrote: > > This version change bumps the library soname from libyaml-cpp.so.0.7 > > to libyaml-cpp.so.0.8. Such an update is not allowed under EPEL > > policy. > > > > https://docs.fedoraproject.org/en-US/epel/epel-policy/#package_maintenance_and_update_policy > > > > If you feel this update is important, you can request an exception via > > the Incompatible Upgrades policy. > > > > https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/ > > > > On Tue, Sep 2, 2025 at 5:41 PM Richard Shaw <hobbes1069@xxxxxxxxx> wrote: > >> > >> I have a request[1] to update yaml-cpp to 0.8.0 in EPEL 10 and have verified the deps build in a copr[2]. > >> > >> If there are no objections I will commence building this coming weekend. > >> > >> Thanks, > >> Richard > >> > >> [1] https://bugzilla.redhat.com/show_bug.cgi?id=2387197 > >> [2] https://copr.fedorainfracloud.org/coprs/hobbes1069/yaml-cpp/builds/ > >> -- > >> _______________________________________________ > >> 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 > > > > > > > > > -- > Orion Poplawski > he/him/his - surely the least important thing about me > IT Systems Manager 720-772-5637 > NWRA, Boulder/CoRA Office FAX: 303-415-9702 > 3380 Mitchell Lane orion@xxxxxxxx > Boulder, CO 80301 https://www.nwra.com/ > -- > _______________________________________________ > 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
