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/
[5] https://bugzilla.redhat.com/show_bug.cgi?id=2307084
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
