Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Mattia Rizzolo Newsgroups: linux.debian.maint.python Subject: Re: Numpy migration? Date: Sat, 05 Jan 2019 16:50:02 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Sat Jan 5 15:40:16 2019 Old-Return-Path: X-Amavis-Spam-Status: No, score=-11.9 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -3.5 Mail-Followup-To: debian-python@lists.debian.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="zCKi3GIZzVBPywwA" Content-Disposition: inline X-Info: Keep It Simple, Stupid. X-Operating-System: Linux, kernel 4.19.0-1-amd64, inside Debian GNU/Linux buster/sid sid. X-Message-Flag: WARNING!! Outlook sucks. A lot. User-Agent: Every email client sucks, this one just sucks less. X-Mailing-List: archive/latest/16657 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20190105153949.GC26988@mapreri.org Approved: robomod@news.nic.it Lines: 60 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sat, 5 Jan 2019 16:39:50 +0100 X-Original-Message-ID: <20190105153949.GC26988@mapreri.org> X-Original-References: <87a7kfqk65.fsf@orrococo> <87y37zp24n.fsf@orrococo> Xref: csiph.com linux.debian.maint.python:11206 --zCKi3GIZzVBPywwA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 05, 2019 at 04:15:04PM +0100, Ole Streicher wrote: > There is one more problem, which are transitional dependencies: >=20 > 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 >=20 > Breaks: python3-astropy (<< fixed-version) >=20 > 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". :) --=20 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=3Dmattia `- --zCKi3GIZzVBPywwA Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAlwwz8MACgkQCBa54Yx2 K61esg/9GqKaqfFPYF/tyYZrVIXDJjwVwUngtMF+5My+Y3G/+cJNlVow3rBjw8lg 9yK0VEwHzeLraTCPj0i7yg98zdaanl/hu5CNLycDiR0mCCiZQcsrwBFLnLkGZSq9 Hmsnl37YzIUSatv/+qfqfYnb0Ieri24wWa2wcQCjF23uAgE5P/yF6ogXg5o44Vik g7TKlOvPwz19BR2iK34dL0pKAOBcuvMoLw1ye3iIYD1K/P69HSyzHPL/fhjH+VRW e6EhscXVgr8k6MrU7ra3W+As7Ej3fzMsnDYWS5i721/TZZub6iU+R3/yaoiCsIu3 OmDfpFyfFFs2r03nymRtxSAZ4oQTLD2bl/ZMlDInFY3QIjiW0SG1nSkHUSQGzad3 be2uPFMSDI9vOHkjmrZUkjimo4KtOytJIzhXtvskYhBvsC61biRsi3eCMpsc5JDG J9QXVjSEQJeCW2+UvjomvB5D8BpItomNXHi6Bj0VrGDcl0m4WEbtXfxlf23yU0Uv gLkQgkXV9OB9KQQ02Yuf2CBCuAfCcximx67tjjKDuun9ZRq6l2il2pVyXcPRDqBg LzY2a4X8lxZNiKltMKXHeQl8YeTg/vAbgClTMRiwB7jQmghF9SYgTDRLwPjrNApo 4ZzOKK91d6l3wPz4Ln1Z7KEF50DBSbWDD/DyIJ4L96yW8BlrMjE= =bxN5 -----END PGP SIGNATURE----- --zCKi3GIZzVBPywwA--