Mattia Rizzolo <mat...@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
