Fedora Account System
Red Hat Associate
Red Hat Customer
python-azure-mgmt-datamigration fails to build with Python 3.15.0a7. This issue appears in all azure-mgmt packages ______________ ERROR collecting tests/test_mgmt_datamigration.py _______________ tests/test_mgmt_datamigration.py:21: in <module> from devtools_testutils import AzureMgmtTestCase, ResourceGroupPreparer /usr/lib/python3.15/site-packages/devtools_testutils/__init__.py:17: in <module> from .keyvault_preparer import KeyVaultPreparer /usr/lib/python3.15/site-packages/devtools_testutils/keyvault_preparer.py:39: in <module> DEFAULT_PERMISSIONS = Permissions( /usr/lib/python3.15/site-packages/azure/mgmt/keyvault/models/_models.py:2791: in __init__ super().__init__(*args, **kwargs) /usr/lib/python3.15/site-packages/azure/mgmt/keyvault/_utils/model_base.py:607: in __init__ raise TypeError(f"{class_name}.__init__() got an unexpected keyword argument '{non_attr_kwargs[0]}'") E TypeError: Permissions.__init__() got an unexpected keyword argument 'keys' https://docs.python.org/3.15/whatsnew/3.15.html For the build logs, see: https://copr-be.cloud.fedoraproject.org/results/@python/python3.15/fedora-rawhide-x86_64/10243153-python-azure-mgmt-datamigration/ For all our attempts to build python-azure-mgmt-datamigration with Python 3.15, see: https://copr.fedorainfracloud.org/coprs/g/python/python3.15/package/python-azure-mgmt-datamigration/ 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.15: https://copr.fedorainfracloud.org/coprs/g/python/python3.15/ Let us know here if you have any questions. Python 3.15 is planned to be included in Fedora 45. To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.15. 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.
This, in fact, is not related to Python 3.15 - Koschei tracks this failure in Fedora 44/Rawhide.
Thanks for the report. This is unfortunately because the Azure Python SDK team uses https://pypi.org/project/azure-devtools/ (which is in their mega-repo where they release all their Python packages from) but they don't release that test package anymore and they clearly _do_ break APIs at random times. This, combined with the fact that azure-cli pins dependencies to both extremely new alpha releases from the SDK and extremely old (many years) packages makes it... challenging to package. I'm going to assume if I pull in a snapshot of azure-devtools from rather recently it'll probably fix this, but there's also a good chance other things will break. I'll give it a go, but to be honest I'm of the opinion we should either not run the tests, have azure-cli bundle its azure SDK packages so we can update all the SDK components as they release, or remove it all from the distribution.
*** Bug 2485773 has been marked as a duplicate of this bug. ***
I've spent some time on this and filed https://github.com/Azure/azure-sdk-for-python/issues/47397. The current state of things appear to be an incredible mess and I'm thinking I'll disable the tests for the packages using this (which isn't great), or retire them and the Azure CLI.
Hello, Please note that this comment was generated automatically by https://forge.fedoraproject.org/releng/tooling/src/branch/main/release-process/bug-filing/follow-policy/follow_policy.py If you feel that this output has mistakes, please open an issue at https://forge.fedoraproject.org/releng/tickets/issues 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.