In one week, 2024-02-04, or slightly later, I plan to update abseil-cpp from 20230802.1 to 20230116.0 (Abseil LTS branch, Jan 2024)[1] in side tags for F40/Rawhide. If I miss getting the update into Rawhide before F40 branching, I plan to do the update in both F41/Rawhide and F40/Branched.
Like all new calendar versions of abseil-cpp, this breaks ABI compatibility and bumps the SONAME version. There are also some small intentional breaking API changes[2].
Testing in COPR[3] indicates all directly-dependent packages are compatible, except mozc, which can be fixed by a PR[4].
Besides abseil-cpp, I plan to rebuild all dependent packages using maintainer/co-maintainer or provenpackager privileges. I also plan to merge the mozc PR if it is still open. These packages are:
- bear - bloaty - credentials-fetcher - CuraEngine_grpc_definitions - fastnetmon - fcitx5-mozc - frr - grpc - ilbc - libarrow - libphonenumber - mozc - onnxruntime - parlaylib - plasma-dialer - qmlkonsole - qt6-qtgrpc - spacebar - syslog-ng
Of these, I expect plasma-dialer and syslog-ng to FTBFS in the side tag since they already FTBFS in Rawhide.
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 the package yourself, or you have other questions or concerns, please just let me know before 2024-02-04.
– Ben Beasley (FAS: music)
[1] https://src.fedoraproject.org/rpms/abseil-cpp/pull-request/16
[2] https://github.com/abseil/abseil-cpp/releases/tag/20240116.0
[3] https://copr.fedorainfracloud.org/coprs/music/abseil-cpp/packages/
Hello, Ben.
On Sunday, 28 January 2024 at 19:43, Ben Beasley wrote:
In one week, 2024-02-04, or slightly later, I plan to update abseil-cpp from 20230802.1 to 20230116.0 (Abseil LTS branch, Jan 2024)[1] in side tags for
Correct me if I'm wrong, but this looks like a downgrade: $ rpmdev-vercmp 0 20230802.1 1 0 20230116.0 1 0:20230802.1-1 > 0:20230116.0-1
Did you mean "update to 20240116.0"?
Regards, Dominik
On 29-01-2024 11:16, Dominik 'Rathann' Mierzejewski wrote:
Hello, Ben.
On Sunday, 28 January 2024 at 19:43, Ben Beasley wrote:
In one week, 2024-02-04, or slightly later, I plan to update abseil-cpp from 20230802.1 to 20230116.0 (Abseil LTS branch, Jan 2024)[1] in side tags for
Correct me if I'm wrong, but this looks like a downgrade: $ rpmdev-vercmp 0 20230802.1 1 0 20230116.0 1 0:20230802.1-1 > 0:20230116.0-1
Did you mean "update to 20240116.0"?
He did, see ${subject}.
Sorry for the late action. I've merged PR for mozc.
Thanks,
On Mon, Jan 29, 2024 at 3:43 AM Ben Beasley code@musicinmybrain.net wrote:
In one week, 2024-02-04, or slightly later, I plan to update abseil-cpp from 20230802.1 to 20230116.0 (Abseil LTS branch, Jan 2024)[1] in side tags for F40/Rawhide. If I miss getting the update into Rawhide before F40 branching, I plan to do the update in both F41/Rawhide and F40/Branched.
Like all new calendar versions of abseil-cpp, this breaks ABI compatibility and bumps the SONAME version. There are also some small intentional breaking API changes[2].
Testing in COPR[3] indicates all directly-dependent packages are compatible, except mozc, which can be fixed by a PR[4].
Besides abseil-cpp, I plan to rebuild all dependent packages using maintainer/co-maintainer or provenpackager privileges. I also plan to merge the mozc PR if it is still open. These packages are:
- bear - bloaty - credentials-fetcher - CuraEngine_grpc_definitions - fastnetmon - fcitx5-mozc - frr - grpc - ilbc - libarrow - libphonenumber - mozc - onnxruntime - parlaylib - plasma-dialer - qmlkonsole - qt6-qtgrpc - spacebar - syslog-ngOf these, I expect plasma-dialer and syslog-ng to FTBFS in the side tag since they already FTBFS in Rawhide.
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 the package yourself, or you have other questions or concerns, please just let me know before 2024-02-04.
– Ben Beasley (FAS: music)
[1] https://src.fedoraproject.org/rpms/abseil-cpp/pull-request/16
[2] https://github.com/abseil/abseil-cpp/releases/tag/20240116.0
[3] https://copr.fedorainfracloud.org/coprs/music/abseil-cpp/packages/
The rebuild is complete, and the side tag is merged via [1]. As of this writing, it is waiting on test gating.
Including parlaylib was an error on my part, since it is header-only and none of its binary packages depend on abseil-cpp. Nevertheless, parlaylib started to FTBFS in Rawhide after the initial announcement and before the rebuild, so I filed a bug[2].
The syslog-ng package already failed in the mass rebuild[3] because it FTBFS on i686[4], which is related to the Change PortingToModernC[5]. Since I knew rebuilding this package would fail (and a scratch build confirmed this[6] and showed that it actually fails on *all* architectures now), I did not bother to push a rebuild commit. Note that dropping i686 support from syslog-ng would require dropping it in perl-Unix-Syslog and therefore in a number of other packages. This is still probably feasible. I expect that syslog-ng-opentelemetry will now FTI until the package can be rebuilt in Rawhide and (post-branching) F40[7]. I am in contact with the syslog-ng maintainers via Bugzilla and have offered my assistance if they run into any trouble.
All other packages were successfully rebuilt.
If you think I missed something, let me know and I’ll help clean it up!
[1] https://bodhi.fedoraproject.org/updates/FEDORA-2024-ce6bbab91a
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2262661
[3] https://bugzilla.redhat.com/show_bug.cgi?id=2261744
[4] https://bugzilla.redhat.com/show_bug.cgi?id=2258853
[5] https://fedoraproject.org/wiki/Changes/PortingToModernC#Use_of_incompatible_...
[6] https://koji.fedoraproject.org/koji/taskinfo?taskID=112924642
[7] https://bugzilla.redhat.com/show_bug.cgi?id=2261744#c8
On 1/28/24 13:43, Ben Beasley wrote:
In one week, 2024-02-04, or slightly later, I plan to update abseil-cpp from 20230802.1 to 20230116.0 (Abseil LTS branch, Jan 2024)[1] in side tags for F40/Rawhide. If I miss getting the update into Rawhide before F40 branching, I plan to do the update in both F41/Rawhide and F40/Branched.
Like all new calendar versions of abseil-cpp, this breaks ABI compatibility and bumps the SONAME version. There are also some small intentional breaking API changes[2].
Testing in COPR[3] indicates all directly-dependent packages are compatible, except mozc, which can be fixed by a PR[4].
Besides abseil-cpp, I plan to rebuild all dependent packages using maintainer/co-maintainer or provenpackager privileges. I also plan to merge the mozc PR if it is still open. These packages are:
- bear - bloaty - credentials-fetcher - CuraEngine_grpc_definitions - fastnetmon - fcitx5-mozc - frr - grpc - ilbc - libarrow - libphonenumber - mozc - onnxruntime - parlaylib - plasma-dialer - qmlkonsole - qt6-qtgrpc - spacebar - syslog-ng
Of these, I expect plasma-dialer and syslog-ng to FTBFS in the side tag since they already FTBFS in Rawhide.
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 the package yourself, or you have other questions or concerns, please just let me know before 2024-02-04.
– Ben Beasley (FAS: music)
[1] https://src.fedoraproject.org/rpms/abseil-cpp/pull-request/16
[2] https://github.com/abseil/abseil-cpp/releases/tag/20240116.0
[3] https://copr.fedorainfracloud.org/coprs/music/abseil-cpp/packages/
-
Akira TAGOH -
Ben Beasley -
Dominik 'Rathann' Mierzejewski -
Sandro