Your message dated Sat, 24 Aug 2024 08:35:25 +0000 with message-id <e1shmf3-00bdd7...@fasolo.debian.org> and subject line Bug#1078540: fixed in scipy 1.14.0-1exp2 has caused the Debian Bug report #1078540, regarding special: libsf_error_state.so: cannot open shared object file to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1078540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: python3-scipy Version: 1.14.0-1exp1 Severity: serious Justification: debci scipy 1.14 builds libsf_error_state.so for the special submodule, from sf_error_state.c, sf_error_state.h The meson build controls are sf_error_state_lib = shared_library('sf_error_state', ['sf_error_state.c'], include_directories: ['../_lib', '../_build_utils/src'], c_args: scipy_export_dll_args, install: true, install_dir: py3.get_install_dir() / 'scipy/special', ) so it's intended as a shared library. dh_python3 (or maybe pybuild) finds it and converts libsf_error_state.so to libsf_error_state.cpython-312-x86_64-linux-gnu.so Then at runtime (or during tests) we get an error when accessing special e.g. $ python3 -c "import scipy.special" Traceback (most recent call last): File "<string>", line 1, in <module> File "/usr/lib/python3/dist-packages/scipy/special/__init__.py", line 807, in <module> from . import _ufuncs ImportError: libsf_error_state.so: cannot open shared object file: No such file or directory lintian also reports an error: W: python3-scipy: shared-library-lacks-prerequisites [usr/lib/python3/dist-packages/scipy/special/libsf_error_state.cpython-312-x86_64-linux-gnu.so] N: N: The listed shared library doesn't include information about the other libraries against which it was linked. N: N: More specifically, "ldd foo.so" should report such other libraries. In your case, it reports "statically linked". N: N: The fix is to specify the libraries. One way to do so is to add something like "-lc" to the command-line options for "ld". sf_error_state.c does not use python as such. As far as I can see libsf_error_state.so is intended to be an actual shared library, not a python extension. In that case it should not be renamed to libsf_error_state.cpython-312-x86_64-linux-gnu.so Indeed if I manually changed it back to libsf_error_state.so then special works as normal. Not sure what the best fix is, since multilib is involved together with sonames. _ufuncs.cpython-312-x86_64-linux-gnu.so is a "normal" python extension in special, objdump -p shows it has NEEDED libsf_error_state.so Perhaps libsf_error_state.so could be moved to /usr/lib/<arch_triplet>/. Alternatively perhaps the soname could be changed to libsf_error_state_<arch_triplet>.so, keeping it in the scipy/special dir. Moving it to the standard lib path in /usr/lib/ might arguably be simpler (not sure if it's easy to get meson to embed an arch-triplet in the soname)
--- End Message ---
--- Begin Message ---Source: scipy Source-Version: 1.14.0-1exp2 Done: Drew Parsons <dpars...@debian.org> We believe that the bug you reported is fixed in the latest version of scipy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1078...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons <dpars...@debian.org> (supplier of updated scipy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sat, 24 Aug 2024 02:16:41 +0200 Source: scipy Architecture: source Version: 1.14.0-1exp2 Distribution: experimental Urgency: medium Maintainer: Debian Python Team <team+pyt...@tracker.debian.org> Changed-By: Drew Parsons <dpars...@debian.org> Closes: 1078540 Changes: scipy (1.14.0-1exp2) experimental; urgency=medium . * debian/rules: shift scipy/special/libsf_error_state.so to libsf_error_state while running dh_python3. It is a "normal" shared library not a python extension, but dh_python3 would rename it as if it were a python extension, causing runtime failure finding the library. dh_python3 -X does not exclude that (see Bug#1079496). Closes: #1078540. * mips64el powerpc ppc64: skip test_cython (special test_extending) Needs complex type changes from numpy 2 to pass. See https://github.com/scipy/scipy/issues/21393 * skip more failing tests - mips64el: test_2x2_input (linalg test_matfuncs.py::TestExpM) - hppa: more test_QRVS_shape_consistency variants - x32: TestKSTwoSamples.test_gh12218 (gets MemoryError) Checksums-Sha1: cc2a19d1dd8f89563cb9da4b5a25e6aed87388f2 3412 scipy_1.14.0-1exp2.dsc 8329ea6e16204883527d3e69e6063e8364bb8436 110848 scipy_1.14.0-1exp2.debian.tar.xz Checksums-Sha256: faa36e3da2e664d08d52dbc78633bc38ca01a20e6b642518762c2bbe9b000a1a 3412 scipy_1.14.0-1exp2.dsc 3ecf38b90939dd568d3390c0fec0784457c8b37421b654494ea8f41a889c2e1b 110848 scipy_1.14.0-1exp2.debian.tar.xz Files: 56bfe6a5d8f5996e2d5bbeff319c90cc 3412 python optional scipy_1.14.0-1exp2.dsc f9c181fa0a402d51663f565f00cb0115 110848 python optional scipy_1.14.0-1exp2.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmbJlDwACgkQVz7x5L1a Afp4ARAAgFYhrwFaRFjwjPCM7hJXVdBvGPMgMX8ELAuMw46+JKavTTXqkmsJCxTu OURcczJ5HaOAtwduhhyH+YtqQf7YMpd+xbDZOJdU0atbjb7AcB/SzjZCJWwUD0Eh Mwqix0cmc3CdqVhkfBdjAloPINwLUm3Kn3GTyFfQvK4sNSdJ6cJ+ynHTJjHPxqXH I2ZMO+GX7pr11LlszDeZ7pk782NNRXbdkP57l+sBlXGLL93SZRgOec1shrUXt+5d MPzaO4k9cgMo7N6szu8uZmN3TOop+XUQV1VDqx7QT8Ee39kKk0Q/pzVXVxc3UjcK +MlNcsII2MOTjI7hUXSptF0Qd28kG68Wq/KqimidB4/YXeJvpcxZKLTF1WhALcrN WWFIyVQvSyuQvUld55q8DxZDtcMAglPXYyC3DJ+jS3b+b3IDtaHf6l0Rlr28aHRi PDjYyPpPo+GiD+RHRKFX/TneQTJ2HJ7tcf/AdzJoYZMiW8EizStZx3JX7gwE2knM Z99uy/7clbWwVQyStstP3bbr+ScfJh8m5VDSju5xLp+CgrgURxhg1YDbfS1PkwQo ktoFT4R/4W/R1u80+lWUn7rtVfEFIjC/+MS0vL5YZcxOjn35T0eo+wl1P6AFByDq TP9AIhZiEX2UFdv5D+00BsUABYvO31WAO5sdO7/mvfvNUvsS/IM= =+JDR -----END PGP SIGNATURE-----
pgp5THs53XL00.pgp
Description: PGP signature
--- End Message ---
