In one week (2024-05-06), or slightly later, I plan to update the
rapidyaml package to 0.6.0[1] and the c4core package to 0.2.0[2] in
F41/Rawhide. This includes an SONAME version bump in both cases, with
specific breaking changes documented in the upstream release
notes[3][4]. An impact check in COPR did not reveal any problems[5].
I will use a side tag for the update, and I will rebuild dependent
packages c4fs and c4log as primary maintainer. Unless I’m asked not to,
I will also rebuild jsonnet using provenpackager privilege. No other
packages should be affected.
[1] https://src.fedoraproject.org/rpms/rapidyaml/pull-request/2
[2] https://src.fedoraproject.org/rpms/c4core/pull-request/9
[3] https://github.com/biojppm/rapidyaml/releases/tag/v0.6.0
[4] https://github.com/biojppm/c4core/releases/tag/v0.2.0
[5] https://copr.fedorainfracloud.org/coprs/music/rapidyaml/packages/
--
_______________________________________________
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
