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 `-
signature.asc
Description: PGP signature