Re: Numpy migration?

2019-01-06 Thread Mattia Rizzolo
On Sun, Jan 06, 2019 at 06:19:15PM +0100, Steffen Möller wrote:
> > 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=arm64=3.0-1=1530124204=0)
> - also because of some Numpy issue if I get this right:

Looks so indeed.  However it builds on reproducible (on arm64), and the
error is the same on mips and mips64el, so I asked for the build to be
retried.
However there is after that a different RC bug (that I can fix once the
build is confirmed to be fixed as well).

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature


Re: Numpy migration?

2019-01-06 Thread Steffen Möller



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=arm64=3.0-1=1530124204=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




Re: Numpy migration?

2019-01-06 Thread Ole Streicher
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. Pyregion just got an upload with a fix, but will
probably only migrate after numpy (which will not migrate until
python-astropy is removed).

Now it turns out that there is a new migration problem, which is aplpy:
Current aplpy (2.0~rc2-2) CI test works well

 - with numpy-1.15.4-2 (testing) and matplotlib-2.2.2-4 (testing),
 - with numpy-1.16.0~rc2-1 (unstable) and matplotlib-3.0.2-2 (unstable).

However it does not work well when combining numpy-1.16.0~rc2 (unstable)
and matplotlib-2.2.2-4 (testing), which is the combination that is
tested for migration of numpy. Needless to say that matplotlib migrates
only after numpy. What should one do here? Declaring another
"Breaks: matplotlib (<< 3.0)" in numpy?

Best

Ole