In one week, 2025-02-25, or slightly later, I plan to update abseil-cpp
from 20240722.1 to 20250127.0 (Abseil LTS branch, January 2025)[1] in
side tags for F43/Rawhide. Like all new calendar versions of abseil-cpp,
this breaks ABI compatibility and bumps the SONAME version[2].
Testing in COPR[3] indicates all directly-dependent packages are
compatible, with a few PR’s mentioned later in this message. It’s also
still possible to ship this update in F42/Branched at this point in the
release cycle, but I don’t currently plan to do so. (The release notes
didn’t provide much motivation.)
Besides abseil-cpp, I plan to rebuild all dependent packages using
maintainer/co-maintainer or provenpackager privileges. These packages are:
- bloaty
- buildbox
- credentials-fetcher
- CuraEngine_grpc_definitions
- fastnetmon
- fcitx5-mozc
- frr
- grpc
- ilbc
- libarrow
- libphonenumber
- mozc
- onnxruntime
- parlaylib
- plasma-dialer
- re2
- syslog-ng
- webrtc-audio-processing
In order to do so, I will need to merge these three PR’s, although I am
happy to accept feedback or alternative proposals in the coming week:
- https://src.fedoraproject.org/rpms/onnxruntime/pull-request/9
- https://src.fedoraproject.org/rpms/mozc/pull-request/7
- https://src.fedoraproject.org/rpms/fcitx5-mozc/pull-request/6
It looks like webrtc-audio-processing only ends up using "header-only"
parts of the abseil-cpp API, and doesn’t currently link any abseil-cpp
shared libraries; still, including it in the list above does no harm and
might do some good.
Finally, it looks like marble has a legitimate direct BuildRequires on
abseil-cpp-devel (in that the build system checks for it), but none of
the headers are included and none of the binary packages ends up linking
abseil-cpp libraries, so I see no reason to rebuild marble.
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).
If you want to handle the rebuild of one of the packages in the above
list yourself, or if you have other questions or concerns, please just
let me know before 2025-02-25.
While looking for reverse dependencies, I identified two packages that
had BuildRequires on abseil-cpp-devel but did not actually use it
directly, and whose binary packages did not depend on abseil-cpp. I
opened PR’s to remove these BuildRequires, but these don’t need to be
merged as part of the update or with any particular urgency.
- https://src.fedoraproject.org/rpms/parlaylib/pull-request/1
- https://src.fedoraproject.org/rpms/spacebar/pull-request/4
– Ben Beasley (FAS: music)
[1] https://src.fedoraproject.org/rpms/abseil-cpp/pull-request/26
[2] https://github.com/abseil/abseil-cpp/releases/tag/20250127.0
[3] https://copr.fedorainfracloud.org/coprs/music/abseil-cpp/packages/
--
_______________________________________________
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
