Path: csiph.com!feeder.erje.net!2.eu.feeder.erje.net!news.uzoreto.com!newsfeed.CARNet.hr!news.spin.it!bofh.it!news.nic.it!robomod
From: Ole Streicher <olebole@debian.org>
Newsgroups: linux.debian.maint.python
Subject: Re: Numpy migration?
Date: Sat, 05 Jan 2019 16:40:01 +0100
Message-ID: <xcWdj-78E-3@gated-at.bofh.it>
References: <xcUXT-6rf-5@gated-at.bofh.it> <xcVhg-6xW-9@gated-at.bofh.it>
X-Mailbox-Line: From debian-python-request@lists.debian.org  Sat Jan  5 15:33:08 2019
Old-Return-Path: <news@liska.ath.cx>
X-Amavis-Spam-Status: No, score=-6.999 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no
X-Policyd-Weight: using cached result; rate: -5.5
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Lines: 27
X-Mailing-List: <debian-python@lists.debian.org> archive/latest/16655
List-ID: <debian-python.lists.debian.org>
List-URL: <https://lists.debian.org/debian-python/>
List-Archive: https://lists.debian.org/msgid-search/87y37zp24n.fsf@orrococo
Approved: robomod@news.nic.it
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Date: Sat, 05 Jan 2019 16:15:04 +0100
X-Original-Message-ID: <87y37zp24n.fsf@orrococo>
X-Original-References: <87a7kfqk65.fsf@orrococo> <CAHKYmesvBOg=0cg3A==ei01GeJeJwEjUMfrSa4uSYiT-hk2q_g@mail.gmail.com>
Xref: csiph.com linux.debian.maint.python:11204

Mattia Rizzolo <mattia@debian.org> writes:
> The way forward in cases like these is for the package that originally
> cuased the breakage (i.e. numpy) to declare a versioned Breaks on the
> borken and now fixed package (i.e. astropy (<< 3.1-1)). This way
> britney and debci will know they have to test numpy and astropy
> together, and will be able to correctly migrate to testing at the same
> time, and properly avoid a situation when two incompatible packages
> are installed.
> Maybe you could open a bug on numpy to get the maintainer to add the breaks.

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.

So, how to handle this?

Cheers

Ole