Bug 2084190 - epel9 backport of python-google-api-core
Summary: epel9 backport of python-google-api-core
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: python-google-api-core
Version: 40
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jonathan Wright
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2053630
Blocks: 2082082
TreeView+ depends on / blocked
 
Reported: 2022-05-11 15:53 UTC by Major Hayden 🤠
Modified: 2025-02-25 22:32 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-25 22:32:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Major Hayden 🤠 2022-05-11 15:53:29 UTC
I'd like to get google-api-core backported to epel9, but it has a sizeable dependency list.

Here's a visual map: https://cdn.major.io/google-api-core-dep-map.png

Comment 1 Major Hayden 🤠 2022-05-11 16:52:57 UTC
Quick messaround in COPR reveals some interesting dependencies:

* grpc
    * gevent
        * python-zope-event ✅
        * python-zope-interface
            * python3-docs (could we skip docs?)
            * repoze-sphinx-autointerface (could we skip docs?)
    * oauth2client ✅
        * python-fasteners ✅
    * xds-protos
        * grpcio-tools (but this comes from grpc? 🤔)
        * opencensus-proto
            * grpcio-tools
        * opentelemetry-proto 😱
            * bleach
            * django
            * flaky
            * opentracing
            * protobuf
            * sphinx
            * sphinx-autodoc-typehints
            * thrift
* proto-plus
    * protobuf >= 3.19 (RHEL 9 has 3.14.0)

Comment 2 Ben Beasley 2022-05-11 18:34:02 UTC
This is not quite as scary as it looks. There are some bootstrapping loops that can already be broken by build conditionals, and some optional dependencies that could be pruned until the backports are ready.

I fell behind on updating grpc in Rawhide for a few months due to segfaults in the tests starting with 1.42.0. I finally found time to debug the crashes and send a couple of PR’s upstream. I just announced 1.46.0 for Rawhide, and I’ll be opening the side tag this weekend after the one-week notice period.

I’ve also been helping get the dependencies for grpc in EPEL9. We’re actually very close, I think. I’m planning to spin up a grpc/EPEL9 copr for testing in the coming week or so and try to get the last dependencies in place.

Comment 3 Major Hayden 🤠 2022-05-11 19:21:19 UTC
Thanks for that, Ben. If there's anything I can do to help, just give me a shout.

Comment 4 Ben Beasley 2022-05-23 20:08:54 UTC
I did a local mock build against https://copr.fedorainfracloud.org/coprs/music/grpc-epel9/. Once grpc is in EPEL9, you’ll only have the following to contend with:

> No matching package to install: 'python3dist(grpcio-gcp)'
> No matching package to install: 'python3dist(proto-plus)'

which are both your own packages, so they should be pretty easy to handle.

For

> * proto-plus
>     * protobuf >= 3.19 (RHEL 9 has 3.14.0)

I think you’ll just have to backport proto-plus 1.19.6, which was the last release before the protobuf minimum version was bumped.

For similar reasons, python-googleapis-common-protos is already held back at 1.56.0 instead of 1.56.1 in EPEL9 and can be expected to stay there indefinitely. Considering that all the essential libraries in this stack break their ABIs on every release, I think most of these packages are not likely to see a lot of updates in EPEL9 in the long term.

Comment 5 Major Hayden 🤠 2022-05-24 12:06:16 UTC
Understood! Thanks for making that dependency tree so much easier to handle. 🫂

Comment 6 Ben Cotton 2022-08-09 13:38:38 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.

Comment 7 Aoife Moloney 2023-11-23 00:11:45 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 8 Aoife Moloney 2023-12-05 21:06:52 UTC
Fedora Linux 37 entered end-of-life (EOL) status on None.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 9 Fedora Admin user for bugzilla script actions 2023-12-16 00:11:54 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 10 Fedora Admin user for bugzilla script actions 2023-12-19 00:12:20 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 11 Aoife Moloney 2024-02-15 22:55:02 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle.
Changing version to 40.

Comment 12 Major Hayden 🤠 2025-02-25 22:32:49 UTC
I no longer need this backported.


Note You need to log in before you can comment on or make changes to this bug.