Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #11972 > unrolled thread
| Started by | Hugo Lefeuvre <hle@debian.org> |
|---|---|
| First post | 2019-11-02 09:20 +0100 |
| Last post | 2019-11-02 10:40 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.maint.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#936214: bleachbit: Python2 removal in sid/bullseye Hugo Lefeuvre <hle@debian.org> - 2019-11-02 09:20 +0100
Bug#936214: bleachbit: Python2 removal in sid/bullseye Matthias Klose <doko@debian.org> - 2019-11-02 10:40 +0100
| From | Hugo Lefeuvre <hle@debian.org> |
|---|---|
| Date | 2019-11-02 09:20 +0100 |
| Subject | Bug#936214: bleachbit: Python2 removal in sid/bullseye |
| Message-ID | <yXWDU-3Xe-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
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?
regards,
Hugo
--
Hugo Lefeuvre (hle) | www.owl.eu.com
RSA4096_ 360B 03B3 BF27 4F4D 7A3F D5E8 14AA 1EB8 A247 3DFD
ed25519_ 37B2 6D38 0B25 B8A2 6B9F 3A65 A36F 5357 5F2D DC4C
[toc] | [next] | [standalone]
| From | Matthias Klose <doko@debian.org> |
|---|---|
| Date | 2019-11-02 10:40 +0100 |
| Message-ID | <yXY30-4Hk-3@gated-at.bofh.it> |
| In reply to | #11972 |
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
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web