In one week (2024-09-05), or slightly later, I plan to update the rapidyaml package to 0.7.2[1] in F42/Rawhide and F41/Branched; I will also update its support library c4core to 0.2.2[2]. Both are ABI-breaking updates with SONAME version bumps. I will also update the unversioned support library c4fs to its latest snapshot[3] and rebuild c4log. An impact check in COPR did not reveal any problems[4].
I will use side tags for these updates, using provenpackager privilege to rebuild the sole dependent package, jsonnet.
I’m also planning to use these versions for the initial EPEL10 releases[5] of these packages.
[1] https://src.fedoraproject.org/rpms/rapidyaml/pull-request/3
[2] https://src.fedoraproject.org/rpms/c4core/pull-request/10
[3] https://src.fedoraproject.org/rpms/c4fs/pull-request/4
[4] https://copr.fedorainfracloud.org/coprs/music/rapidyaml/packages/
In one week (2025-02-22), or slightly later, I plan to update the rapidyaml package to 0.8.0[1] in F43/Rawhide and F42/Branched. This is an ABI-breaking update with an SONAME version bump; there are also some API-breaking changes, some of which might be behavioral (only detectable by runtime tests)[2]. The update does, however, fix several bugs. I already impact-checked this update with local mock builds on x86_64 and did not see any problems; I will repeat the impact check in COPR[3] shortly.
I will use side tags for these updates, using provenpackager privilege to rebuild the sole dependent package, jsonnet.
[1] https://src.fedoraproject.org/rpms/rapidyaml/pull-request/4
[2] https://github.com/biojppm/rapidyaml/blob/v0.8.0/changelog/0.8.0.md
[3] https://copr.fedorainfracloud.org/coprs/music/rapidyaml/packages/
-
Ben Beasley