Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #11211

Re: Numpy migration?

From Steffen Möller <steffen_moeller@gmx.de>
Newsgroups linux.debian.maint.python
Subject Re: Numpy migration?
Date 2019-01-06 18:20 +0100
Message-ID <xdkfE-59P-3@gated-at.bofh.it> (permalink)
References (2 earlier) <xcVU0-72b-53@gated-at.bofh.it> <xcWdj-78E-1@gated-at.bofh.it> <xd07g-14F-17@gated-at.bofh.it> <xd4DT-3V8-1@gated-at.bofh.it> <xdjtf-4Df-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 06.01.19 17:07, Ole Streicher wrote:
> Mattia Rizzolo <mattia@debian.org> writes:
>
>> On Sat, Jan 05, 2019 at 08:30:28PM +0100, Ole Streicher wrote:
>>> This would remove one dependent party (release team) from the chain of
>>> blocking causes for the migration.
>> Given your email on -mentors a few minutes ago I see there are troubles
>> on removing python-astropy from unstable (I'll reply to that in a bit),
>> but for testing is quite easy.
>> Just file a bug against release.debian.org asking to remove it from
>> testing, and one against python-astropy at RC-level with "not release
>> with buster", and it will be out of testing beofore you even notice.
> The reverse build deps of python-astropy in testing are pyregion and
> veusz. Veusz has the build-dep removed in unstable, but didn't migrate
> since 192 days.
This is because it does not build on arm64 and others 
(https://buildd.debian.org/status/fetch.php?pkg=veusz&arch=arm64&ver=3.0-1&stamp=1530124204&raw=0) 
- also because of some Numpy issue if I get this right:

dpkg-buildpackage
-----------------

dpkg-buildpackage: info: source package veusz
dpkg-buildpackage: info: source version 3.0-1
dpkg-buildpackage: info: source distribution unstable
  dpkg-source --before-build veusz-3.0
dpkg-buildpackage: info: host architecture arm64
  fakeroot debian/rules clean
dh clean --with python3,sphinxdoc --buildsystem=pybuild
    dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py clean
Traceback (most recent call last):
   File "/usr/lib/python3/dist-packages/numpy/core/__init__.py", line 16, in <module>
     from . import multiarray
ImportError: cannot import name 'multiarray' from 'numpy.core' (/usr/lib/python3/dist-packages/numpy/core/__init__.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
   File "setup.py", line 31, in <module>
     import numpy
   File "/usr/lib/python3/dist-packages/numpy/__init__.py", line 142, in <module>
     from . import add_newdocs
   File "/usr/lib/python3/dist-packages/numpy/add_newdocs.py", line 13, in <module>
     from numpy.lib import add_newdoc
   File "/usr/lib/python3/dist-packages/numpy/lib/__init__.py", line 8, in <module>
     from .type_check import *
   File "/usr/lib/python3/dist-packages/numpy/lib/type_check.py", line 11, in <module>
     import numpy.core.numeric as _nx
   File "/usr/lib/python3/dist-packages/numpy/core/__init__.py", line 26, in <module>
     raise ImportError(msg)
ImportError:
Importing the multiarray numpy extension module failed.  Most
likely you are trying to import a failed build of numpy.
If you're working with a numpy git repo, try `git clean -xdf` (removes all
files not under version control).  Otherwise reinstall numpy.

Original error was: cannot import name 'multiarray' from 'numpy.core' (/usr/lib/python3/dist-packages/numpy/core/__init__.py)

E: pybuild pybuild:336: clean: plugin distutils failed with: exit code=1: python3.7 setup.py clean
dh_auto_clean: pybuild --clean -i python{version} -p "3.7 3.6" returned exit code 13
debian/rules:22: recipe for target 'clean' failed
make: *** [clean] Error 25
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2
--------------------------------------------------------------------------------
Build finished at 2018-06-27T18:29:58Z

Finished
--------

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Numpy migration? Ole Streicher <olebole@debian.org> - 2019-01-05 15:20 +0100
  Re: Numpy migration? Mattia Rizzolo <mattia@debian.org> - 2019-01-05 15:40 +0100
    Re: Numpy migration? Ole Streicher <olebole@debian.org> - 2019-01-05 16:20 +0100
      Re: Numpy migration? Mattia Rizzolo <mattia@debian.org> - 2019-01-05 16:40 +0100
        Re: Numpy migration? Ole Streicher <olebole@debian.org> - 2019-01-05 20:50 +0100
          Re: Numpy migration? Scott Kitterman <debian@kitterman.com> - 2019-01-05 21:00 +0100
          Re: Numpy migration? Mattia Rizzolo <mattia@debian.org> - 2019-01-06 01:40 +0100
            Re: Numpy migration? Ole Streicher <olebole@debian.org> - 2019-01-06 17:30 +0100
              Re: Numpy migration? Steffen Möller <steffen_moeller@gmx.de> - 2019-01-06 18:20 +0100
                Re: Numpy migration? Mattia Rizzolo <mattia@debian.org> - 2019-01-06 18:50 +0100
              Re: Numpy migration? Mattia Rizzolo <mattia@debian.org> - 2019-01-06 19:00 +0100
                Re: Numpy migration? Ole Streicher <olebole@debian.org> - 2019-01-07 09:30 +0100
                Re: Numpy migration? Mattia Rizzolo <mattia@debian.org> - 2019-01-07 17:30 +0100
                Re: Numpy migration? Ole Streicher <olebole@debian.org> - 2019-01-07 18:10 +0100
                Re: Numpy migration? Paul Gevers <elbrus@debian.org> - 2019-01-07 21:10 +0100
    Re: Numpy migration? Ole Streicher <olebole@debian.org> - 2019-01-05 16:40 +0100
      Re: Numpy migration? Mattia Rizzolo <mattia@debian.org> - 2019-01-05 16:50 +0100

csiph-web