Description of problem: can grpc be branched for EPEL8? Version-Release number of selected component (if applicable): latest How reproducible:100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: The most recent version of GRPC on EPEL8 would be wonderful....
Fedora maintainer here. I’d like this too. I took over the grpc package in Fedora early this year, and spent the first few months improving the Fedora package and getting grpc 1.37.x in Rawhide. While working on grpc 1.37.x for Fedora, I got dependencies abseil-cpp and python-googleapis-common-protos branched for EPEL8. (I’m now maintaining abseil-cpp for EPEL.) I’m planning to update Rawhide again to 1.38.x (https://bugzilla.redhat.com/show_bug.cgi?id=1974484), but it’s taking a little while to deal with a new circular dependency, python-xds-protos, which is generated from grpc sources but also is a dependency for two new Python subpackages—plus, it overlaps with existing packages python-opencensus-proto and python-googleapis-common-protos, so the files already provided by those packages have to be disentangled. All of that is tedious but workable, and it’s likely I’ll have that update ready in the next few weeks. For EPEL8, the existing bug is here (https://bugzilla.redhat.com/show_bug.cgi?id=1757147). Unfortunately, the version of protobuf in RHEL8/CentOS8 is too old for vaguely-recent releases of grpc. Using a bundled copy of a later protobuf may be a viable way forward; I am undecided on whether this is wise. If I do bundle protobuf, there will surely be other dependencies that also need to be branched for EPEL8, and the release packaged for EPEL8 would be 1.37.1. This is because 1.38 requires a later abseil-cpp LTS version than the one I branched for EPEL8, and I am unwilling to bundle abseil just to get 1.38. (Abseil-cpp breaks ABI every LTS release, and grpc breaks ABI pretty much every minor release, so significant updates in stable branches are not generally possible.) Suggestions and assistance are welcome. Please direct questions to one of the existing issues I’ve linked. Thanks! *** This bug has been marked as a duplicate of bug 1757147 ***