Automatic update for re2-20240702-1.fc41.
* Tue Aug 13 2024 Denis Arnaud <denis.arnaud_fedora@m4x.org> - 1:20240702-1
- Upgrade to 2024-07-02
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2024-82d9eb51a1Please login to add feedback.
This update was automatically created
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update has been submitted for stable by bodhi
Bugzilla related ticket: https://bugzilla.redhat.com/show_bug.cgi?id=2304069
This update comes with a version bump and should therefore have been announced on the devel mailing list. Previous version provided
libre2.so.9()(64bit). This version provideslibre2.so.11()(64bit), resulting in:I just saw your message on the devel mailing list. I sincerely apologize for that. If you know a way to revert the update, do not hesitate. Also, you are more than welcome to co-maintain that package.
I suppose the solution is to rebuild dependent packages against the updated
re2. But that should have happened in a side tag before pushing the update. Right now Koji is offline since releng is busy with branching f41. So, we have to sit this one out.Regarding co-maintainership, you seem to be offering that to everyone stumbling upon
re2. I'm not directly impacted byre2, but indirectly vialibarrow. And I'm already co-maintaining a bunch of other packages.If you feel you can no longer keep up with maintaining
re2or do not feel up to the task, it would be best to orphan the package, so someone else can take over. If yo do so, I'd recommend you announce your intentions on the devel mailing list. There's no shame in that and others will surely understand.For now, leave it as is. Maintainers of impacted packages will notice and hopefully know what to do (rebuild their package(s) in rawhide). Let's hope the dependent packages will rebuild against the new version without breaking.
It looks like a simple rebuild won't do. I ran a smoke test, rebuilding all packages that directly depend on
re2with the new release:https://copr.fedorainfracloud.org/coprs/gui1ty/re2/builds/
Everything that failed, I rebuilt again against the current version:
https://copr.fedorainfracloud.org/coprs/gui1ty/re2-x-check/builds/
If it fails in the first, but succeeds in the second, it's a strong indication of
re2being the culprit. To make matters worse,grpcis currently FTBFS for unrelated reasons. Since some of the packages also depend ongrpc, it's not possible to tell if the newerre2would cause any issues for those.I'm afraid you may need to revert the update or ask releng to pull it from rawhide. It requires more work and above all coordination to land it there. I'm not sure it can be pulled, though, since it is now in the newly branched f41 as well, if I'm not mistaken.
Message sent to rel-eng mailing list in an attempt to block this update to reach F41 repositories: https://lists.fedoraproject.org/archives/list/rel-eng@lists.fedoraproject.org/thread/RFNBZBZ47S7LNVR25FK6DH6BOMAJQUUQ/
Ben Beasley has been rebuilding gRPC on Fedora 42 and Fedora 41, as posted on the Fedora Devel mailing list: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/EZRZHVBQQU7ZV7QQ5JEBCI37SDP7XFCA/
Further references, as provided by Ben: * gRPC for Fedora Rawhide (F42): https://koji.fedoraproject.org/koji/taskinfo?taskID=121948781 * gRPC for Fedora 41 (F41): https://koji.fedoraproject.org/koji/taskinfo?taskID=121948783 * Commit on the Fedora package source for gRPC: https://src.fedoraproject.org/rpms/grpc/c/2f7c688380196227334a331cfc701bc5e203157c?branch=rawhide