Intent to update yaml-cpp in 10.1

[Richard Shaw]

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/

[Carl George]

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_a...

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  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 -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]...
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Orion Poplawski]

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_a...
>
> 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  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 -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]...
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Carl George]

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  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_a...
> >
> > 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  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 -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]...
> > > 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: [phone]
> 3380 Mitchell Lane                       [e-mail]
> Boulder, CO 80301                 https://www.nwra.com/
> --
> _______________________________________________
> epel-devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]...
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Orion Poplawski]

On 9/2/25 16:40, Richard Shaw 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 <https:// 
> bugzilla.redhat.com/show_bug.cgi?id=2387197>
> [2] https://copr.fedorainfracloud.org/coprs/hobbes1069/yaml-cpp/builds/ 
> https://copr.fedorainfracloud.org/coprs/hobbes1069/yaml-cpp/builds/

I'd like to drive this forward.  I note my reasons and some notes form 
the requests above:

yaml-cpp 0.8.0 is the minimum supported by libmamba 2.0+ - the current 
solver for the conda packaging ecosystem.  I feel EPEL10 would be very 
crippled if it could not support it.  libmamba 1.X has stopped receiving 
updates and would be pointless to ship at this point.

The current deps for yaml-cpp are:

OpenColorIO-0:2.4.2-6.el10_2.x86_64
lhapdf-0:6.5.5-1.el10_0.x86_64
pdns-ixfrdist-0:5.0.1-1.el10_2.x86_64
qt-creator-0:16.0.2-2.el10_2.x86_64
rocm-validation-suite-0:6.4.2-2.el10_2.x86_64

I've rebuilt these deps in a copr:

https://copr.fedorainfracloud.org/coprs/orion/yaml-cpp-epel10/builds/

and they all rebuild fine.

I'm also willing to package up a yaml-cpp-0.7 compatibility package for 
EPEL10 if needed.  Or alternatively I suppose I could build a 
yaml-cpp-0.8, but the former seems more forward looking.

I have filed a ticket here: https://pagure.io/epel/issue/359

[Richard Shaw]

On Thu, Nov 27, 2025 at 12:01 PM Orion Poplawski  wrote:
> I have filed a ticket here: https://pagure.io/epel/issue/359

I'm guessing there's no SLA to respond to a ticket but it's been 4 days...
I can see "17 subscribers" so minus us there's 15 people and no one has
responded yet.

Should silence be taken for acceptance after a week?

Thanks,
Richard

[Troy Dawson]

On Tue, Dec 2, 2025 at 4:42 AM Richard Shaw  wrote:
> On Thu, Nov 27, 2025 at 12:01 PM Orion Poplawski  wrote:
> > I have filed a ticket here: https://pagure.io/epel/issue/359
>
> I'm guessing there's no SLA to respond to a ticket but it's been 4 days...
> I can see "17 subscribers" so minus us there's 15 people and no one has
> responded yet.
>
> Should silence be taken for acceptance after a week?
>
> Thanks,
> Richard

No, but thanks for the reminder.
We plan on discussing it at this weeks EPEL Steering Committee meeting.
Troy

[Neal Gompa]

On Tue, Dec 2, 2025 at 7:42 AM Richard Shaw  wrote:
> On Thu, Nov 27, 2025 at 12:01 PM Orion Poplawski  wrote:
> > I have filed a ticket here: https://pagure.io/epel/issue/359
>
> I'm guessing there's no SLA to respond to a ticket but it's been 4 days... I can see "17 subscribers" so minus us there's 15 people and no one has responded yet.
>
> Should silence be taken for acceptance after a week?

Most EPSco members were away last week and the week before, which is
probably why nobody saw it yet.

[Troy Dawson]

On Thu, Nov 27, 2025 at 10:02 AM Orion Poplawski  wrote:
> On 9/2/25 16:40, Richard Shaw 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 https://
> > bugzilla.redhat.com/show_bug.cgi?id=2387197
> > [2] https://copr.fedorainfracloud.org/coprs/hobbes1069/yaml-cpp/builds/
> > https://copr.fedorainfracloud.org/coprs/hobbes1069/yaml-cpp/builds/
>
> I'd like to drive this forward.  I note my reasons and some notes form
> the requests above:
>
> yaml-cpp 0.8.0 is the minimum supported by libmamba 2.0+ - the current
> solver for the conda packaging ecosystem.  I feel EPEL10 would be very
> crippled if it could not support it.  libmamba 1.X has stopped receiving
> updates and would be pointless to ship at this point.
>
> The current deps for yaml-cpp are:
>
> OpenColorIO-0:2.4.2-6.el10_2.x86_64
> lhapdf-0:6.5.5-1.el10_0.x86_64
> pdns-ixfrdist-0:5.0.1-1.el10_2.x86_64
> qt-creator-0:16.0.2-2.el10_2.x86_64
> rocm-validation-suite-0:6.4.2-2.el10_2.x86_64
>
> I've rebuilt these deps in a copr:
>
> https://copr.fedorainfracloud.org/coprs/orion/yaml-cpp-epel10/builds/
>
> and they all rebuild fine.

I just found out that qt6 in CentOS Stream 10 will be updated in this
monday's release (Dec  8)
Because of that, qt-creator will need to be rebuilt next week in EPEL10
That is not a blocker for this, I'm just letting you know so that we can
plan and co-ordinate rebuilds of qt-creator.

Troy