Hi Andreas, On 13.09.19 10:45, Andreas Tille wrote: > On Fri, Sep 13, 2019 at 09:56:56AM +0200, Ole Streicher wrote: >> Andreas Tille <[email protected]> writes: >>> as Peter Green found out the cloudpickle source package droped Python2 >>> support which makes bug #938494 serious. I guess it would be even >>> harder to drop python-skimage right now since this would affect >>> python-numpy and according to >>> >>> $ apt-cache rdepends python-numpy | sort | uniq | wc -l >>> >>> 339 reverse dependencies. I have no better solution than just pinging >>> bug #938494 from time to time - and to ping this list to work harder on >>> Python3 migration. >> >> Since skimage is team maintained, I will just do a team upload with the >> Python 2 package removed (as member of d-science). > > Sure. But do you want to do team uploads of python-numpy and its > 300 > rdepends as well? I was considering the amount of packages that are > affected by RC bugs which is way lower if we leave skimage RC buggy > rather than making python-numpy RC buggy. I mean, in the end we need to > port everything but we can decide about a noisy mailing list flooding us > every now and than with 300 mails about packages getting removed from > testing or keeping that number at about 20.
I am not sure I understand you here. skimage is now scheduled for autoremoval; I really think we should go forward here. And as far as I remember, numpy is secured from autoremoval, so even an RC buggy numpy will not lead to autoremoval. I now pushed skimage_0.14.2-3 to salsa, with Python 2 removed. Just awaiting the salsa CI tests: shall I upload or shall I wait? We should go forward, shouldn't we? > BTW, you can start with droping rdepends by droping astro-python > metapackage. Oops, I thought that I already uploaded it. Will do ASAP. Cheers Ole -- debian-science-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
