In one week, 2026-03-22, or slightly later, I plan to update rapidyaml
from 0.10.0 to 0.11.0 in F45/Rawhide[1]. This is an API- and
ABI-incompatible update that changes the SONAME version[2].
At the same time, I will update rapidyaml’s support library c4core from
0.2.8 to 0.2.10[3], which is also an API- and ABI-breaking update. This
doesn’t impact anything other than rapidyaml and its support libraries
c4fs and c4log, which I will also rebuild as maintainer.
There is one dependent package, jsonnet. Despite the documented API
changes, it rebuilt successfully in COPR[4]. I will use provenpackager
privilege to rebuild jsonnet in the same side tag.
I am not planning to ship this update for F44/Branched. While it’s
technically feasible, I see no justification for doing so this late in
the release cycle.
– Ben Beasley (FAS: music)
[1] https://src.fedoraproject.org/rpms/rapidyaml/pull-request/7
[2] https://github.com/biojppm/rapidyaml/blob/v0.11.0/changelog/0.11.0.md
[3] https://src.fedoraproject.org/rpms/c4core/pull-request/13
[4] https://copr.fedorainfracloud.org/coprs/music/rapidyaml/packages/
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
