On 02.11.19 09:05, Hugo Lefeuvre wrote:
Hi Matthias, I see that you just raised the severity of this bug to serious, and Bleachbit is now to be removed on 16.11. I don't think this is the way to go. Upstream is actively working on this. We have recently managed the GTK3 migration, meaning that Py3 is now top priority. Loosing Bleachbit would be a significant source of annoyance for many Debian users (popcon 2754 at the moment). May I add the py2keep flag, until the Bleachbit Py3 migration completes?
Hi,thanks for reaching out to debian-python. Unfortunately the pygtk py2removal bug (#937452) didn't see much attention, and I didn't raise the severity of this issue myself, just for the r-deps affecting the Python2 removal. Pygtk will never be ported to Python3, so action is needed for every rdep.
You won't loose Bleachbit just because it's removed from testing for a few weeks/months, and I don't see any rdeps for the package itself. Using the py2keep tag for packages which have a transition plan in place for bullseye seems to be odd, and distracts the view for packages which we apparently need to keep.
Lowering the severity for the bleachbit issue might be a work around, but then unexpected pygtk removal may bite you again.
Matthias