Bug #6327

PyGTK Deprecated in Debian 10

Added by Dave Hibberd 5 months ago.

Status:New Start date:12/27/2018
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:-
Chirp Version:0.4.0 Platform:Linux
Model affected:(All models)

Description

Hi all!

I do packaging work for Debian and noticed in our bugtracker that there's been a bug open for chirp for a while now (text copied below)

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885265

The long & short of it is that the Gnome Team are aiming to remove PyGTK from Debian by the time Buster rolls around (mid 2019).

While this isn't immediately an issue, I worry that by the time we hit new Debian Stable and Ubuntu 19.10, we'll all begin to see bug reports about CHIRP not working on Debian/Ubuntu/Mint/etc.

I appreciate it's a pile of work to port to GTK3+, and I can't quite find if this is definitely going ahead this release cycle, but I figured it was worth raising as a consideration for the future! Even if we lose chirp from the release of debian-nextstable, it'd be great if it kept working in the Debian & Friends sandbox anywau.

Thanks for doing awesome work :D

Cheers,
DH

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.

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

Also available in: Atom PDF