Re: Please do not drop Python 2 modules
- Date: Tue, 24 Apr 2018 09:19:58 +0200
- From: Emilio Pozuelo Monfort <pochu@xxxxxxxxxx>
- Subject: Re: Please do not drop Python 2 modules
On 23/04/18 23:54, Thomas Goirand wrote:
> Also, I have noticed that when removing Python 2 legacy packages, a lot
> of cruft remains in the archive. This isn't trivial to track and clean.
> I'd love to have the opinion of the FTP master team about this. How can
> we file sensible bugs about it? How can I track what hasn't been un-crufted?
If the package that you removed has no reverse dependencies, then it will be
automatically removed (decrufted), and the removal will be mentioned in
If it has rdeps and can't be auto-removed, then it will appear in the cruft report:
But please do not remove packages that have rdeps if you don't have a transition
plan. Otherwise you're just going to cause your package to get stuck in unstable
with no chance to migrate to testing, see e.g.:
By all means start getting your rdeps / python2 apps ported, so that when the
time comes, dropping Python 2 support won't be such a daunting task.