Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #11206
| From | Mattia Rizzolo <mattia@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Numpy migration? |
| Date | 2019-01-05 16:50 +0100 |
| Message-ID | <xcWn0-7cf-13@gated-at.bofh.it> (permalink) |
| References | <xcUXT-6rf-5@gated-at.bofh.it> <xcVhg-6xW-9@gated-at.bofh.it> <xcWdj-78E-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Sat, Jan 05, 2019 at 04:15:04PM +0100, Ole Streicher wrote:
> There is one more problem, which are transitional dependencies:
>
> The new python3-numpy version breaks (f.e.) python3-pyregion because of
> the problem in python3-astropy. The new upload of python3-astropy fixes
> this, so in unstable everything is OK. Even when one now adds a
>
> Breaks: python3-astropy (<< fixed-version)
>
> to python-numpy, it will not migrate due to the test failure of
> python3-pyregion in testing. Adding a "Breaks: python3-pyregion" is
> however wrong, since pyregion is perfect for the new numpy version.
If I understood correctly, pyregion is perfectly fine and needs no
action. In that case, it's not a problem: with the "Breaks:
python3-astropy (<< fixed-ver)" in place, the pyregion test would
install the fixed version of python3-astropy from unstable as the broken
version from testing would not be installable using the numpy from
unstable.
> So, how to handle this?
No action needed once both astropy and numpy are "fixed". :)
--
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 `-
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll 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