In one week, 2023-08-28, I plan to update abseil-cpp from 20230125.3 to
20230802.0 (Abseil LTS branch, Aug 2023)[1] in side tags for F40/Rawhide
and F39/Branched.
Like all new calendar versions of abseil-cpp, this breaks ABI
compatibility and bumps the SONAME version. There are no intentional
breaking API changes[2].
Testing in COPR[3] indicates all directly-dependent packages are
compatible. (A change was required in mozc and fcitx5-mozc, which were
using internal/non-API symbols[4]; the necessary change has already been
discussed with upstream and committed to dist-git.)
Besides abseil-cpp, I will rebuild the following dependent packages as
maintainer or co-maintainer:
bear, fastnetmon, grpc, libarrow (Rawhide only, using collaborator
privileges)
I should be able to build existing commits of the following packages
even though I do not have privileges on the dist-git projects:
fcitx5-mozc, mozc
The following were tested in COPR but do not need to be rebuilt, because
they are header-only and do not link dynamically against abseil-cpp:
parlaylib
I will ask the maintainers of the following to rebuild into the side
tags, asking a provenpackager to help if the maintainers are not able to
follow up within a few days:
bloaty, credentials-fetcher, frr, ilbc, libarrow (F39 only),
libphonenumber, plasma-dialer, qmlkonsole, syslog-ng
If you maintain a package on this final list, please expect another
direct email once the side tags are ready and I have built at least
abseil-cpp and grpc. If you want me to handle rebuilds like this in the
future, you can add me as a co-maintainer (FAS music) with commit
privileges, or at minimum collaborator privileges on the rawhide branch
since these updates will usually happen before branching.
Maintainers of all affected packages should have received this email
directly (by BCC rather than CC, to keep the message from being held for
moderation due to a long CC list).
Finally, those working on the eventual upgrade of protobuf from 3.x to
v4 (22.x/23.x/24.x) should be aware that it looks like we will need to
package a 24.x release for compatibility with this abseil-cpp
release[5][6]. This shouldn’t be a problem; we are nowhere close to
working out all the issues in dependent packages for protobuf v4, which
will certainly not happen in F39, and another rebase of the working
PR[7] will be a trivial effort compared to the other necessary work.
[1] https://src.fedoraproject.org/rpms/abseil-cpp/pull-request/14
[2] https://github.com/abseil/abseil-cpp/releases/tag/20230802.0
[3] https://copr.fedorainfracloud.org/coprs/music/abseil-cpp/packages/
[4] https://bugzilla.redhat.com/show_bug.cgi?id=2231905
[5] https://github.com/google/mozc/issues/790#issuecomment-1679915315
[6] https://github.com/protocolbuffers/protobuf/pull/13534/files
[7] https://src.fedoraproject.org/rpms/protobuf/pull-request/25
_______________________________________________
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
