Package: python-numpy Version: 1:1.16.2-1 Severity: important Dear Maintainer,
since the laste upload of pymca, the autopkgtest are failing[1]. After an investigation, this bug is visible only with the python-dbg interpreters[3] testFastFitEdfMap (PyMcaBatchTest.testPyMcaBatch) ... Thread 1 "python3.7-dbg" received signal SIGSEGV, Segmentation fault. prepare_index (self=self@entry=0x7fffc0349d40, index=index@entry= ([False, False, False, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True], <ellipsis at remote 0x8225c0>), indices=indices@entry=0x7fffffffa9a0, num=num@entry=0x7fffffffa97c, ndim=ndim@entry=0x7fffffffa980, out_fancy_ndim=out_fancy_ndim@entry=0x7fffffffa984, allow_boolean=<optimized out>) at numpy/core/src/multiarray/mapping.c:634 634 numpy/core/src/multiarray/mapping.c: No such file or directory. the backtrace #0 0x00007ffff6b731e0 in prepare_index (self=self@entry=0x7fffc0349d40, index=index@entry=([False, False, False, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True], <ellipsis at remote 0x8225c0>), indices=indices@entry=0x7fffffffa9a0, num=num@entry=0x7fffffffa97c, ndim=ndim@entry=0x7fffffffa980, out_fancy_ndim=out_fancy_ndim@entry=0x7fffffffa984, allow_boolean=<optimized out>) at numpy/core/src/multiarray/mapping.c:634 #1 0x00007ffff6b770d8 in array_subscript (self=0x7fffc0349d40, op=([False, False, False, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True], <ellipsis at remote 0x8225c0>)) at numpy/core/src/multiarray/mapping.c:1600 #2 0x0000000000603d8a in PyObject_GetItem (o=o@entry=<numpy.ndarray at remote 0x7fffc0349d40>, key=key@entry=([False, False, False, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True, True], <ellipsis at remote 0x8225c0>)) at ../Objects/abstract.c:154 this bug was already fixed by the upsteam here[2]. Is it possible to fix this in unstable and evaluate if this should be proposed as a buster update. thanks for considering Frederic [1] https://ci.debian.net/data/autopkgtest/testing/amd64/p/pymca/2614899/log.gz [2] https://github.com/numpy/numpy/pull/13715 [3] https://github.com/vasole/pymca/issues/539 -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python-numpy depends on: ii libatlas3-base [liblapack.so.3] 3.10.3-8 ii libblas3 [libblas.so.3] 3.8.0-2 ii libc6 2.28-10 ii liblapack3 [liblapack.so.3] 3.8.0-2 ii libopenblas-base [liblapack.so.3] 0.3.5+ds-3 ii python 2.7.16-1 ii python-pkg-resources 40.8.0-1 ii python2.7 2.7.16-2 python-numpy recommends no packages. Versions of packages python-numpy suggests: ii gcc 4:8.3.0-1 ii gfortran 4:8.3.0-1 ii python-dev 2.7.16-1 ii python-numpy-dbg 1:1.16.2-1 ii python-numpy-doc 1:1.16.2-1 ii python-pytest 3.10.1-2 -- no debconf information
