Re: google-re2 pacakge update and facebook vs google python bindings ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I’m not aware of anything in grpc that would require re2 to be held back. If there is, I’d hope it could be resolved.

An impact check in COPR would be wise for any update.

I’ve CC’d the appropriate aliases to make sure *all* of the maintainers of the re2 and python-fb-re2 packages are aware of this conversation.

On 2/6/24 13:36, Paul Wouters wrote:

Hi,

At $dayjob we are running into issues with re2 and python bindings.

Fedora has a fairly old version of re2 with so.9 while upstream is at
so.11. Is there a reason for this? If it is just time, I'd like to
help bumping the package in rawhide.

Originally, facebook creating python bindings for this, which are
packaged in python-fb-re2, but this package is no longer updated
as google're2 now has native python bindings (I think the fb one
was pulled in and maintained and so the fb one is abandoned upsteam)

I'd like to see:

- google-re2 updated to version 2024-02-04
- python3-google-re2 python bindings shipped, providing the fb-re2 package.
- python2-fb-re2 retired

Currently, the google-re2 python bindings do not compile against
the older google-re2 we ship (but that might be a fairly trivial
fix, that would need to be done for the branches anyway)


Added package maintainers to the CC: for additional input.


Again, happy to help if time/effort is the only thing holding
this back. If there are other reasons for this, I'd very much
like to know more. I know there were soname issues in the past.

Packages that would be affected by the soname bump:

loaty
dnsdist
frr
grpc
libarrow
mtxclient
onnxruntime
perl-re-engine-RE2
python3-fb-re2
python3-grpcio
python3-onnxruntime
qt5-qtwebengine
syslog-ng
syslog-ng-opentelemetry

Thanks,

Paul
--
_______________________________________________
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
--
_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux