Bug 2280563 - python-google-cloud-monitoring fails to build with Python 3.13: TypeError: Couldn't build proto file into descriptor pool!
Summary: python-google-cloud-monitoring fails to build with Python 3.13: TypeError: Co...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: python-google-cloud-monitoring
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orphan Owner
QA Contact:
URL:
Whiteboard:
: 2291725 (view as bug list)
Depends On:
Blocks: F41FTBFS F42FailsToInstall PYTHON3.13 F41FailsToInstall
TreeView+ depends on / blocked
 
Reported: 2024-05-15 07:20 UTC by Karolina Surma
Modified: 2024-12-22 04:25 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-08-23 13:01:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Karolina Surma 2024-05-15 07:20:33 UTC
python-google-cloud-monitoring fails to build with Python 3.13.0b1.

+ /usr/bin/python3 -sP /usr/lib/rpm/redhat/import_all_modules.py -f /builddir/build/BUILD/python-google-cloud-monitoring-2.19.1-1.fc41.x86_64-pyproject-modules
Check import: google
Check import: google.cloud
Check import: google.cloud.monitoring
Traceback (most recent call last):
  File "/usr/lib/rpm/redhat/import_all_modules.py", line 171, in <module>
    main()
    ~~~~^^
  File "/usr/lib/rpm/redhat/import_all_modules.py", line 167, in main
    import_modules(modules)
    ~~~~~~~~~~~~~~^^^^^^^^^
  File "/usr/lib/rpm/redhat/import_all_modules.py", line 100, in import_modules
    importlib.import_module(module)
    ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^
  File "/usr/lib64/python3.13/importlib/__init__.py", line 88, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 1021, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "/builddir/build/BUILDROOT/python-google-cloud-monitoring-2.19.1-1.fc41.x86_64/usr/lib/python3.13/site-packages/google/cloud/monitoring/__init__.py", line 21, in <module>
    from google.cloud.monitoring_v3.services.alert_policy_service.async_client import (
        AlertPolicyServiceAsyncClient,
    )
  File "/builddir/build/BUILDROOT/python-google-cloud-monitoring-2.19.1-1.fc41.x86_64/usr/lib/python3.13/site-packages/google/cloud/monitoring_v3/__init__.py", line 21, in <module>
    from .services.alert_policy_service import (
    ...<2 lines>...
    )
  File "/builddir/build/BUILDROOT/python-google-cloud-monitoring-2.19.1-1.fc41.x86_64/usr/lib/python3.13/site-packages/google/cloud/monitoring_v3/services/alert_policy_service/__init__.py", line 16, in <module>
    from .async_client import AlertPolicyServiceAsyncClient
  File "/builddir/build/BUILDROOT/python-google-cloud-monitoring-2.19.1-1.fc41.x86_64/usr/lib/python3.13/site-packages/google/cloud/monitoring_v3/services/alert_policy_service/async_client.py", line 49, in <module>
    from google.cloud.monitoring_v3.services.alert_policy_service import pagers
  File "/builddir/build/BUILDROOT/python-google-cloud-monitoring-2.19.1-1.fc41.x86_64/usr/lib/python3.13/site-packages/google/cloud/monitoring_v3/services/alert_policy_service/pagers.py", line 27, in <module>
    from google.cloud.monitoring_v3.types import alert, alert_service
  File "/builddir/build/BUILDROOT/python-google-cloud-monitoring-2.19.1-1.fc41.x86_64/usr/lib/python3.13/site-packages/google/cloud/monitoring_v3/types/__init__.py", line 16, in <module>
    from .alert import AlertPolicy
  File "/builddir/build/BUILDROOT/python-google-cloud-monitoring-2.19.1-1.fc41.x86_64/usr/lib/python3.13/site-packages/google/cloud/monitoring_v3/types/alert.py", line 26, in <module>
    from google.cloud.monitoring_v3.types import common
  File "/builddir/build/BUILDROOT/python-google-cloud-monitoring-2.19.1-1.fc41.x86_64/usr/lib/python3.13/site-packages/google/cloud/monitoring_v3/types/common.py", line 227, in <module>
    class Aggregation(proto.Message):
    ...<412 lines>...
        )
  File "/usr/lib/python3.13/site-packages/proto/message.py", line 275, in __new__
    file_info.generate_file_pb(new_class=cls, fallback_salt=full_name)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.13/site-packages/proto/_file_info.py", line 104, in generate_file_pb
    pool.Add(self.descriptor)
    ~~~~~~~~^^^^^^^^^^^^^^^^^
TypeError: Couldn't build proto file into descriptor pool!
Invalid proto descriptor for file "google/cloud/monitoring_v3/types/common.proto":
  google.monitoring.v3.Aggregation.__firstlineno__: "__firstlineno__" is already defined in "google.monitoring.v3.Aggregation".
  google.monitoring.v3.Aggregation.__firstlineno__: Note that enum values use C++ scoping rules, meaning that enum values are siblings of their type, not children of it.  Therefore, "__firstlineno__" must be unique within "google.monitoring.v3.Aggregation", not just within "Reducer".
  google.monitoring.v3.__firstlineno__: "__firstlineno__" is already defined in "google.monitoring.v3".
  google.monitoring.v3.__firstlineno__: Note that enum values use C++ scoping rules, meaning that enum values are siblings of their type, not children of it.  Therefore, "__firstlineno__" must be unique within "google.monitoring.v3", not just within "ServiceTier".

https://docs.python.org/3.13/whatsnew/3.13.html

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.13/fedora-rawhide-x86_64/07443579-python-google-cloud-monitoring/

For all our attempts to build python-google-cloud-monitoring with Python 3.13, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.13/package/python-google-cloud-monitoring/

Testing and mass rebuild of packages is happening in copr.
You can follow these instructions to test locally in mock if your package builds with Python 3.13:
https://copr.fedorainfracloud.org/coprs/g/python/python3.13/

Let us know here if you have any questions.

Python 3.13 is planned to be included in Fedora 41.
To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.13.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires),
so if this package is required a lot, it's important for us to get it fixed soon.

We'd appreciate help from the people who know this package best,
but if you don't want to work on this now, let us know so we can try to work around it on our side.

Comment 1 Karolina Surma 2024-06-12 15:02:08 UTC
*** Bug 2291725 has been marked as a duplicate of this bug. ***

Comment 2 Fedora Fails To Install 2024-06-19 19:59:38 UTC
Hello,

Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/

This package fails to install and maintainers are advised to take one of the following actions:

 - Fix this bug and close this bugzilla once the update makes it to the repository.
   (The same script that posted this comment will eventually close this bugzilla
   when the fixed package reaches the repository, so you don't have to worry about it.)

or

 - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet.

or

 - Orphan the package if you no longer plan to maintain it.


If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue.
This package may be orphaned in 7+ weeks.
This is the first reminder (step 3) from the policy.

Don't hesitate to ask for help on https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ if you are unsure how to fix this bug.

Comment 3 Fedora Fails To Install 2024-07-13 08:01:47 UTC
Hello,

Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/

This package fails to install and maintainers are advised to take one of the following actions:

 - Fix this bug and close this bugzilla once the update makes it to the repository.
   (The same script that posted this comment will eventually close this bugzilla
   when the fixed package reaches the repository, so you don't have to worry about it.)

or

 - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet.

or

 - Orphan the package if you no longer plan to maintain it.


If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue.
This package may be orphaned in 4+ weeks.
This is the second reminder (step 4) from the policy.

Don't hesitate to ask for help on https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ if you are unsure how to fix this bug.

Comment 4 Fedora Fails To Install 2024-08-13 00:02:32 UTC
This package has been orphaned.

You can pick it up at https://src.fedoraproject.org/rpms/python-google-cloud-monitoring by clicking button "Take". If nobody picks it up, it will be retired and removed from a distribution.

Comment 5 Fedora Admin user for bugzilla script actions 2024-08-22 18:42:18 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 6 Miro Hrončok 2024-08-23 13:01:38 UTC
Automation has figured out the package is retired in rawhide.

If you like it to be unretired, please open a ticket at https://pagure.io/releng/new_issue?template=package_unretirement

Comment 7 Red Hat Bugzilla 2024-12-22 04:25:12 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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