[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#42081: closed ([PATCH] Upgrade xpra to 4.0.2)

From: GNU bug Tracking System
Subject: bug#42081: closed ([PATCH] Upgrade xpra to 4.0.2)
Date: Mon, 13 Jul 2020 10:56:02 +0000

Your message dated Mon, 13 Jul 2020 12:55:42 +0200
with message-id <87mu43smz5.fsf@gnu.org>
and subject line Re: [bug#42081] [PATCH] Upgrade xpra to 4.0.2
has caused the debbugs.gnu.org bug report #42081,
regarding [PATCH] Upgrade xpra to 4.0.2
to be marked as done.

(If you believe you have received this mail in error, please contact

42081: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=42081
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH] Upgrade xpra to 4.0.2 Date: Sat, 27 Jun 2020 15:26:55 +0200

the following patchset upgrade xpra to version 4.0.2, which will finally
use Python 3 and GTK 3. It removes the Python 2 variants of PyOpenGL,
because xpra is the only dependent. I’ve been running this package for a
week now and connected to both version 4 and version 3 on an Ubuntu
machine, which still works. OpenGL also works, despite failing tests for

Rutger: You have been working on xpra in the past. Could you take a
look and make sure I did not break any use case?


Attachment: 0001-gnu-Add-python-pyopengl.patch
Description: Text Data

Attachment: 0004-gnu-xpra-Upgrade-to-4.0.2.patch
Description: Text Data

Attachment: 0002-gnu-Add-python-pyopengl-accelerate.patch
Description: Text Data

Attachment: 0006-gnu-python2-pyopengl-Remove.patch
Description: Text Data

Attachment: 0003-gnu-Add-xf86-video-dummy.patch
Description: Text Data

Attachment: 0005-gnu-python2-pyopengl-accelerate-Remove.patch
Description: Text Data

--- End Message ---
--- Begin Message --- Subject: Re: [bug#42081] [PATCH] Upgrade xpra to 4.0.2 Date: Mon, 13 Jul 2020 12:55:42 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)

Lars-Dominik Braun <lars@6xq.net> skribis:

>> Rutger has been inactive in Guix for a few months (last commit in
>> Sep. 2019).  If these patches work for you, I suggest applying them.
>> If it turns out to break another use case, we can always fix it up
>> afterwards.
> oh, I did not know that. Sure, go ahead and feel free to CC me if any
> problems arise.

I’ve pushed the whole series after building everything on x86_64-linux.



--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]