https://bugzilla.suse.com/show_bug.cgi?id=1230064 Bug ID: 1230064 Summary: GDAL problem: Python3 GDAL needs to be compiled using Numpy 2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs@suse.de Reporter: variablestarlight@gmail.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Tumblweed has recently updated to Numpy 2. It seems that the currently provided GDAL Python module was compiled with Numpy 1.X and would also need to be compiled using Numpy 2.

gdal_merge.py

A module that was compiled using NumPy 1.x cannot be run in NumPy 2.0.0 as it may crash. To support both 1.x and 2.x versions of NumPy, modules must be compiled with NumPy 2.0. Some module may need to rebuild instead e.g. with 'pybind11>=2.12'. If you are a user of the module, the easiest solution will be to downgrade to 'numpy<2' or try to upgrade the affected module. We expect that some modules will need time to support NumPy 2. Traceback (most recent call last): File "/usr/local/bin/gdal_merge.py", line 12, in <module> sys.exit(main(sys.argv)) File "/usr/lib64/python3.11/site-packages/osgeo_utils/gdal_merge.py", line 656, in main return gdal_merge(argv) File "/usr/lib64/python3.11/site-packages/osgeo_utils/gdal_merge.py", line 395, in gdal_merge with gdal.ExceptionMgr(): File "/usr/local/lib64/python3.11/site-packages/osgeo/gdal.py", line 213, in __enter__ from . import gdal_array File "/usr/local/lib64/python3.11/site-packages/osgeo/gdal_array.py", line 10, in <module> from . import _gdal_array Traceback (most recent call last): File "/usr/lib64/python3.11/site-packages/numpy/core/_multiarray_umath.py", line 44, in __getattr__ raise ImportError(msg) ImportError: A module that was compiled using NumPy 1.x cannot be run in NumPy 2.0.0 as it may crash. To support both 1.x and 2.x versions of NumPy, modules must be compiled with NumPy 2.0. Some module may need to rebuild instead e.g. with 'pybind11>=2.12'. If you are a user of the module, the easiest solution will be to downgrade to 'numpy<2' or try to upgrade the affected module. We expect that some modules will need time to support NumPy 2. -- You are receiving this mail because: You are on the CC list for the bug.