Package: python3-numpy Version: 1:1.16.0~rc1-3 Dear Maintainer,
as discussed on debian-python@l.d.o (see below), you should add versioned breaks for the packages that failed in their CI tests because they are incompatible. >From the packages I maintain, this relates to aplpy << 2.0~rc2-1 astropy << 3.1-1 ccdproc << 1.3.0-5 python-astropy << 2.0.9-1+ (wontfix) skimage << 0.14.1-3 (team upload) Please consider adding "Breaks" relations to these packages. Thanks Ole -------- Forwarded Message -------- Subject: Re: Numpy migration? Date: Sat, 5 Jan 2019 15:32:30 +0100 From: Mattia Rizzolo <mat...@debian.org> To: Ole Streicher <oleb...@debian.org> CC: debian-python <debian-pyt...@lists.debian.org> )On Sat, Jan 5, 2019 at 3:18 PM Ole Streicher <oleb...@debian.org> wrote: > However, astropy cannot migrate now, to testing, since it depends on > the new numpy version (and therefore can only migrate after numpy). > And numpy is blocked by the CI failure of astropy ... > > Looks like a deadlock. Which will be resolved before the migration > delay ends. Which is in the second half of february, and therefore > will cause all packages that depend on numpy and are not in testing > yet to be kept outside of Buster (due to the release timeline). Starting from half a month ago CI regressions are de-facto release blockers. 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. BTW, that numpy upload also blocked our effort to remove Python 3.6 from buster...
