Hi all, Since a few days, a new RC is stalled in unstable:
testing: 1:1.15.4-2 unstable: 1:1.16.0~rc1-3 The reason that it can't migrate is that it breaks the CI tests of several packages in testing. For example astropy (where I am the uploader), and its dependencies. The CI test failures were caused by astropy (#917466) and are fixed since a week in unstable. 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). What is the way to resolve those problems? These deadlocks probably appear regularly when a package gets a major update: package A breaks the CI test of the rdep B in testing, and a rebuild of B in unstable depends on the newer version of A. Another CI problem is python-astropy, which is the Python 2 version of Astropy. python-astropy is going to be removed as soon as there are no backward dependencies left; however there is still some cruft in unstable that depends on python-astropy. But this should not hinder numpy to migrate. How to solve this? Best Ole
