Your message dated Mon, 4 Oct 2021 22:58:48 -0400
with message-id 
<CAB4XWXwMPCH6rb5eVA1JUrNTnVz4X17L_XvaQwVCA2a=0hl...@mail.gmail.com>
and subject line Re: Bug#995454: python3-numpy: segfault and core dump with a 
simple "import numpy"
has caused the Debian Bug report #995454,
regarding python3-numpy: segfault and core dump with a simple "import numpy"
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 [email protected]
immediately.)


-- 
995454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995454
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python3-numpy
Version: 1:1.19.5-1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Upgraded servers from Buster to Bullseye

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
Upgraded the whole system. After that, an user reported his script didn't work 
anymore.
Tried
apt purge python3-numpy libboost-numpy*
apt autoremove
apt install python3-numpy libboost-numpy*

   * What was the outcome of this action?
str957-cluster:~$ python3
Python 3.9.2 (default, Feb 28 2021, 17:03:44) 
[GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
Errore di segmentazione (core dump creato)

   * What outcome did you expect instead?
That numpy package got imported


-- System Information:
Debian Release: 11.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/12 CPU threads)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-numpy depends on:
ii  libatlas3-base [liblapack.so.3]        3.10.3-10
ii  libblas3 [libblas.so.3]                3.9.0-3
ii  libc6                                  2.31-13
ii  liblapack3 [liblapack.so.3]            3.9.0-3
ii  libopenblas0-pthread [liblapack.so.3]  0.3.13+ds-3
ii  python3                                3.9.2-3
ii  python3-pkg-resources                  52.0.0-4
ii  python3.9                              3.9.2-1

python3-numpy recommends no packages.

Versions of packages python3-numpy suggests:
ii  gcc                4:10.2.1-1
ii  gfortran           4:10.2.1-1
pn  python-numpy-doc   <none>
ii  python3-dev        3.9.2-3
pn  python3-numpy-dbg  <none>
pn  python3-pytest     <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
>    * What led up to the situation?
> Upgraded servers from Buster to Bullseye
>
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> Upgraded the whole system. After that, an user reported his script didn't 
> work anymore.
> Tried
> apt purge python3-numpy libboost-numpy*
> apt autoremove
> apt install python3-numpy libboost-numpy*
>
>    * What was the outcome of this action?
> str957-cluster:~$ python3
> Python 3.9.2 (default, Feb 28 2021, 17:03:44)
> [GCC 10.2.1 20210110] on linux
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import numpy
> Errore di segmentazione (core dump creato)
>
>    * What outcome did you expect instead?
> That numpy package got imported

i tried on a clean docker image of debian stable and i was able to use
numpy just fine, with the commands you provided. In addition, if numpy
was broken in stable, we'd be seeing a lot more reports, while yours
is the only one, which seems to suggest a local issue.

closing this report as it's not pertinent to numpy, if you need
further help debugging this, i suggest to contact one of the users
support forums at https://www.debian.org/support

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

--- End Message ---

Reply via email to