On Wed, Nov 20, 2019 at 12:57:00PM +0200, Yavor Doganov wrote:
>
> OK, I'll start working on this then and I'll ping you when I'm done (I
> have commit access to debian-med but I'm not a DD). I'll probably
> remove or at least disable Shayan's patch as it is not sufficient and
> this code won't b
On Wed, Nov 20, 2019 at 11:49:44AM +0100, Andreas Tille wrote:
> I guess you have read the past conversation that upstream is not
> willing to port code to GTK 3.
Yes, that's why I don't think it's a good idea for me to attempt
porting it -- the result won't be merged in.
> On Wed, Nov 20, 2019 a
Hi,
I guess you have read the past conversation that upstream is not willing
to port code to GTK 3.
On Wed, Nov 20, 2019 at 12:20:38PM +0200, Yavor Doganov wrote:
>
> IMO the only chance to keep gwyddion in bullseye is to build it with
> the option --disable-pygwy. This will automatically solve
On Sun, Sep 29, 2019 at 08:27:59PM +0100, Shayan Doust wrote:
> Just a notice to those who read this: it seems like with the python2 ->
> python3 migration, python-gtk2-dev becomes redundant and should be avoided.
It's more complex than that. PyGTK is strictly tied to Python 2 and
GTK 2. To move
4 matches
Mail list logo
