Path: csiph.com!3.eu.feeder.erje.net!feeder.erje.net!weretis.net!feeder7.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Matthias Klose Newsgroups: linux.debian.bugs.dist,linux.debian.maint.python,linux.debian.maint.gtk.gnome Subject: Bug#936214: bleachbit: Python2 removal in sid/bullseye Date: Sat, 02 Nov 2019 10:40:02 +0100 Message-ID: References: X-Original-To: Hugo Lefeuvre , 936214@bugs.debian.org X-Mailbox-Line: From debian-bugs-dist-request@lists.debian.org Sat Nov 2 09:39:09 2019 Old-Return-Path: X-Spam-Flag: NO X-Spam-Score: -4.2 Reply-To: Matthias Klose , 936214@bugs.debian.org Resent-To: debian-bugs-dist@lists.debian.org Resent-Cc: Hugo Lefeuvre X-Debian-Pr-Message: followup 936214 X-Debian-Pr-Package: src:bleachbit X-Debian-Pr-Keywords: bullseye sid X-Debian-Pr-Source: bleachbit X-Spam-Bayes: score:0.0000 Tokens: new, 10; hammy, 150; neutral, 71; spammy, 0. spammytokens: hammytokens:0.000-+--python3, 0.000-+--H*F:U*doko, 0.000-+--H*u:60.0, 0.000-+--popcon, 0.000-+--Python3 Old-X-Envelope-From: doko@debian.org User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Debian-Message: from BTS X-Mailing-List: archive/latest/1567076 List-ID: List-URL: Approved: robomod@news.nic.it Lines: 30 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org, debian-gtk-gnome@lists.debian.org X-Original-Date: Sat, 2 Nov 2019 10:34:59 +0100 X-Original-Message-ID: <3db43462-9044-a6e1-6f49-ac9e80eb3561@debian.org> X-Original-References: <20191102080538.xhmgzcm2d57laoml@behemoth.owl.eu.com.local> <20191102080538.xhmgzcm2d57laoml@behemoth.owl.eu.com.local> Xref: csiph.com linux.debian.bugs.dist:981855 linux.debian.maint.python:11973 linux.debian.maint.gtk.gnome:1044 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