Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: On s390x, “import rtree” fails unless spatialindex-devel (which is not a dependency of python3-rtree) is installed. Version-Release number of selected component (if applicable): 0.9.4-6 How reproducible: Steps to Reproduce: 1. $ sudo dnf install qemu-user-static 2. $ mock -r fedora-rawhide-s390x --clean 3. $ mock -r fedora-rawhide-s390x -i python3-rtree 4. $ mock -r fedora-rawhide-s390x --shell 5. # python3 -c 'import rtree' Actual results: > Traceback (most recent call last): > File "<string>", line 1, in <module> > File "/usr/lib/python3.10/site-packages/rtree/__init__.py", line 1, in <module> > from .index import Rtree > File "/usr/lib/python3.10/site-packages/rtree/index.py", line 6, in <module> > from . import core > File "/usr/lib/python3.10/site-packages/rtree/core.py", line 143, in <module> > rt.Error_GetLastErrorNum.restype = ctypes.c_int > File "/usr/lib64/python3.10/ctypes/__init__.py", line 387, in __getattr__ > func = self.__getitem__(name) > File "/usr/lib64/python3.10/ctypes/__init__.py", line 392, in __getitem__ > func = self._FuncPtr((name_or_ordinal, self)) > AttributeError: /usr/bin/python3: undefined symbol: Error_GetLastErrorNum Expected results: (success; no output) Additional info: Exiting the mock chroot and issuing > $ mock -r fedora-rawhide-s390x -i spatialindex-devel fixes the problem. I noticed this while working on python-trimesh. It would be nice if there were some way to patch either python-Rtree or spatialindex such that the library can be found on s390x without the -devel package. If this is not possible, at least adding a “Requires: spatialindex-devel” workaround would be appreciated.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
I can’t seem to reproduce this in F36 or Rawhide/F37 anymore. I’m not sure exactly what fixed it. Maybe it was something in 0.9.7, although I don’t see any changes that would have obviously helped.
FEDORA-2022-7dbf3d7383 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-7dbf3d7383
FEDORA-2022-7dbf3d7383 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.