This issue proposes updating the re2 package from version 20220601 to 20240702 in EPEL10. This would be an ABI-incompatible update that would bump the SONAME version from 9 to 11.
re2
This issue is part of the process for incompatible upgrades. I already sent the prescribed message to the epel-devel list.
epel-devel
In addition to two years of assorted bugfixes, which are mostly only documented in the commit messages, this update would allow us to ship the maintained, official Python bindings as a python3-google-re2 subpackage.
python3-google-re2
While there are a quite a few packages that depend on re2 in Fedora, it’s still a leaf package in EPEL10. I’m hoping that this fact, along with the benefits of shipping a current version with Python bindings and the fact that EPEL10 has not yet been officially launched for end-users, will help make this an uncontroversial proposal.
Sounds like a great idea to me. +1
Metadata Update from @carlwgeorge: - Issue tagged with: meeting
+1
This was discussed in today's EPEL Steering Committee meeting. It was agreed by the committee that this issue would be approved and fast-tracked. What that means is this, in terms of the policy.[1] You had already done steps 1-3 of the policy. The time limit of step 4 was waived. Everyone agreed that there had already been enough discussion. Step 5 passed. Everyone agreed that the incompatible upgrade can be built. Step 7 does not apply to epel10, due to the way builds are processed. Since step 7 is not applied, step 6 and 8 are condensed, and only one email needs to be sent.
Happy Building!!
[1] - https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/#process_for_incompatible_upgrades
Metadata Update from @tdawson: - Issue close_status updated to: Approved - Issue status updated to: Closed (was: Open)
Thank you for the follow-up! I will proceed with the announcement and update in the next day or so, at a time when I have enough availability to see it to completion.
As discussed on Matrix, I’m aware that this is no longer a leaf package in EPEL10 since dependent packages were branched and built in the last couple of days. I will use a side tag and ensure that dependent packages are rebuilt successfully before issuing the update.
Log in to comment on this ticket.