In one week, on 2022-08-21, I plan to update abseil-cpp to 20220623.0[1] and 
grpc to 1.48.0[2] in Rawhide and F37. Both updates contain .so version bumps; 
for grpc, both the C and the C++ .so versions have changed.

Because I want to merge the side tag for these packages in time for the 
2022-08-23 F37 beta freeze, I plan to start doing builds in side tags a couple 
of days before the announced 2022-08-21 update date.

I am in the process of verifying compatibility of dependent packages using 
local mock builds on x86_64; COPR is currently broken due to RPM signature 
issues related to F37 branching. In the unlikely event I find a regression I 
cannot trivially fix, I will delay one or both updates and will leave the PR’s 
unmerged.

The following packages will need to be rebuilt into side tags for F38/Rawhide 
and F37.

- bear (abseil-cpp, grpc)

- bloaty (abseil-cpp)

- fastnetmon (abseil-cpp, grpc)

- fcitx5-mozc (abseil-cpp)

- frr (abseil-cpp, grpc)

- ilbc (abseil-cpp)

- libarrow (grpc)

- mozc (abseil-cpp)

- perl-grpc-xs (grpc)

Maintainers of affected packages should have received this email directly.

I will rebuild bear and libarrow as a co-maintainer. Maintainers of other 
affected packages should expect an email when the side tags are ready. If you 
maintain one of the affected packages and you want me to handle these rebuilds 
in the future, you can add me (FAS music) to the project with “commit” 
privileges.

[1] https://src.fedoraproject.org/rpms/abseil-cpp/pull-request/8

[2] https://src.fedoraproject.org/rpms/grpc/pull-request/14

_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to