Path: csiph.com!weretis.net!feeder7.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: =?UTF-8?Q?Steffen_M=c3=b6ller?= Newsgroups: linux.debian.maint.python Subject: Re: Numpy migration? Date: Sun, 06 Jan 2019 18:20:02 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Sun Jan 6 17:19:29 2019 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.7 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FREEMAIL_FROM=0.001, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:64.0) Gecko/20100101 Thunderbird/64.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Provags-ID: V03:K1:ByU01xQyvRqVLHu+JfpJTbLcMUBioH6XPHaEgBn8zcY4v0bcGSx gPIO+LkXfRgmY9qcrWJDAf2jM2G0fptrcWp7OzF5Ye2dh71WideGeUyxnCxiC5sbVOumU11 j++4lICz4GgowIm6GngoV7zo4S8e+EmsBOLY1OGhm1Hgz4COO0fxvT0rT0yG04rN5qviVog aBqO7hbxRWbYvVcgrc2xA== X-Ui-Out-Filterresults: notjunk:1;V03:K0:r2iD/RSxESo=:BHeXJ1bRqVVeb4jPVeV0H+ XAVf6UxdTI/zvRzjFjc6vCkADcFhjGSDqsHY6tQREi399ydHEFKvZ3nK/VFE68Z3haV9Cszzp cccXIJ9smoQPtBEE8Ms/bagaG1LnCpwZ0zhYCkn/U2dJXLALtoFekE6WRvgFwDGD9pmsXQLnG GF5P6Nk5HsfWbYQRAg0txe/KeGL0xbmSOX2TQL4VNlNKbCT+WGPFNhj/dX4sdUcO4snQmJtp5 mKb6p1VVuQwJ73uOML2noOGbqCYkxgT0NTdX/CyjqVNTPnx6A32TIU2Y8IF8H1CKZp9HMHPa9 0PP3UEn0lftGORu/LK9MlUGM/Es8y2CQOzsyxtyXRZl7HJFQzfa0jYknIpXQk/Nro4H0LnXge Q/9rX8cZpG3cK92TWMLIwa0RG0LCSXaZ7hYT7dLUWDs73JI2ZClLamiGLGglKdPpbAyEj3VVF JDhsnUFIIICdCSnsGsPxwbFeyTm+Zd51In/XWkNzowstOA5JqfTzC4esmvSyTiTyaNDc9EOBC i2JV5o95JurqhqMN3WA+fVaLqzOPnFh1z+MJimMs8yMDnNBnTY/iTXpIJMEwDvZWoNg/6OeEN EzmDalKt8wq/IQcP2TP2fPfgpKdCO5wYl0+aWlsW5DyBkxqsD01+cC0VwdpIGeaz/ZW0D5oyn d8wI0wjCqR83g87O0vUfGsKjAGtMGiR/nyPZWS0usadafF3euSMLr1SNTcaq3Iv91rlkSdf9N JyzYmR21guEjuULSmEoQ7b4ed4gBfQhYsrIw7MoHOGSy7tqRJy/Geal3ozJnTH2kgA0ehuqqg cmByzEgPxfqAH92G6u7RMe3BVBEYtQadr0+JE7p7yw4VBH47GIBycB/Flt3CdYp/M5bg0E2uI xrbB2utUNdO5ECE317znDJVVRHBRLUENY5rIDoVHzkAxy9kc2h3QeZaGSKC347tbD5j93OBku YbU/KxM5K1w== X-Mailing-List: archive/latest/16662 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/8aa37300-7536-2031-fb9a-9958c127b965@gmx.de Approved: robomod@news.nic.it Lines: 70 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sun, 6 Jan 2019 18:19:15 +0100 X-Original-Message-ID: <8aa37300-7536-2031-fb9a-9958c127b965@gmx.de> X-Original-References: <87a7kfqk65.fsf@orrococo> <8736q7qh9w.fsf@orrococo> <20190105153545.GB26988@mapreri.org> <87tvimq4vf.fsf@orrococo> <20190105221009.GA23578@mapreri.org> <87h8elpy5u.fsf@orrococo> Xref: csiph.com linux.debian.maint.python:11211 On 06.01.19 17:07, Ole Streicher wrote: > Mattia Rizzolo 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 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 import numpy File "/usr/lib/python3/dist-packages/numpy/__init__.py", line 142, in from . import add_newdocs File "/usr/lib/python3/dist-packages/numpy/add_newdocs.py", line 13, in from numpy.lib import add_newdoc File "/usr/lib/python3/dist-packages/numpy/lib/__init__.py", line 8, in from .type_check import * File "/usr/lib/python3/dist-packages/numpy/lib/type_check.py", line 11, in import numpy.core.numeric as _nx File "/usr/lib/python3/dist-packages/numpy/core/__init__.py", line 26, in 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 --------