Bug#937052: mirage: Python2 removal in sid/bullseye
I've finished my initial porting efforts and released a 0.10.0 release candidate here: https://gitlab.com/thomasross/mirage/-/tags/0.10.0-rc1 The port isn't perfect yet, it still uses many deprecated functions, but I plan on continuing to maintain Mirage and make it more current as time goes on, this is simply an initial Python3/GTK+3 port. I will be releasing a final 0.10.0 version in the next few days and then begin work on packaging it for Debian. If a DD would like to sponsor the next Mirage upload, please let me know. Thanks! Thomas. Thomas. On Fri, 27 Mar 2020 22:46:38 +0100 =?UTF-8?Q?Moritz_M=C3=BChlenhoff?= wrote: > On Fri, Jan 03, 2020 at 02:42:22AM -0500, Thomas Ross wrote: > > I've started to port Mirage to Python 3 + PyGObject here: > > https://gitlab.com/thomasross/mirage/tree/python3 > > What's the status? If this isn't complete, could we upload > that to experimental and remove mirage from unstable (which > avoids a roundtrip through the NEW queue), mirage is among > the last handful of packages blocking the pygtk removal at > this points. > > Cheers, > Moritz > > signature.asc Description: OpenPGP digital signature
Bug#885353: mirage: Depends on unmaintained pygtk
I've finished my initial porting efforts and released a 0.10.0 release candidate here: https://gitlab.com/thomasross/mirage/-/tags/0.10.0-rc1 The port isn't perfect yet, it still uses many deprecated functions, but I plan on continuing to maintain Mirage and make it more current as time goes on, this is simply an initial Python3/GTK+3 port. I will be releasing a final 0.10.0 version in the next few days and then begin work on packaging it for Debian. If a DD would like to sponsor the next Mirage upload, please let me know. Thanks! Thomas. On Tue, 26 Dec 2017 10:08:13 -0500 Jeremy Bicha wrote: > Source: mirage > Version: 0.9.5.2-1 > Severity: serious > User: pkg-gnome-maintain...@lists.alioth.debian.org > Usertags: oldlibs pygtk > Tags: sid buster > > pygtk is unmaintained upstream. It has not had a release since GNOME 3 > was released in 2011. > > The way forward is to port your app to use GObject Introspection > bindings (and gtk3). > > For more information on GObject Introspection see [1] and [2]. > > Please try to do this before the Buster release as we're going to > try to remove pygtk this cycle. > > If you have any question don't hesitate to ask. > > [1] https://wiki.gnome.org/Projects/GObjectIntrospection > [2] https://wiki.gnome.org/Projects/PyGObject > > On behalf of the Debian GNOME team, > Jeremy Bicha > > signature.asc Description: OpenPGP digital signature
Bug#885353: mirage: Python2 removal in sid/bullseye
I've started to port Mirage to Python 3 + PyGObject here: https://gitlab.com/thomasross/mirage/tree/python3 On Fri, 30 Aug 2019 07:26:43 + Matthias Klose wrote: Package: src:mirage Version: 0.9.5.2-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:mirage If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list.
Bug#885353: bumping severity of pygtk bugs
Since upstream for this project is dead, I intent on porting mirage to Python 3 myself when time allows. As soon as Py3 mirage is ready, I will try to get the new version uploaded. Thanks, Thomas. On Sun, 06 Oct 2019 17:09:30 -0400 Jeremy Bicha wrote: > Control: severity -1 serious > Control: tags -1 -buster > > > As part of the Python2 removal, it is our intent that pygtk will be removed > from Testing before the release of Debian 11 > "Bullseye". Therefore, I am bumping the severity of this bug to Serious to > ensure that there is plenty of warning before > the Debian 11 release and to make the eventual removal of pygtk as smooth as > possible. > > > On behalf of the Debian GNOME team, > Jeremy Bicha signature.asc Description: OpenPGP digital signature
