Hi,
as some of you might already know, I started porting the X2Go Session
Broker and Python X2Go + PyHoca-CLI to Python3 during the X2Go
Gathering 2017. (Unfortunately, Pyhoca-GUI is not yet portable, as
python-wxgtk is not yet available a python3-wxgtk, at least not on my
development system, which is Debian).
The question now is, how to start the transition. The code may still
be flawed here and there, so this requires some thorough phase of
testing.
First, the idea is to have the Python3 ports on the master branches in
Git, while keeping the Python2 code maintained on several release
branches in Git:
Python X2Go: release/0.5.0.x
https://code.x2go.org/gitweb?p=python-x2go.git;a=shortlog;h=refs/heads/relea...
PyHoca-CLI: release/0.5.0.x
https://code.x2go.org/gitweb?p=pyhoca-cli.git;a=shortlog;h=refs/heads/releas...
X2Go Session Broker: release/0.0.3.x
https://code.x2go.org/gitweb?p=x2gobroker.git;a=shortlog;h=refs/heads/releas...
The code has already been pushed to those branches, however, the
builds fail on various old distros. Mostly, due to missing Python3
dependencies (e.g. python3-gevent is missing in Debian jessie, but a
requirement for python3-x2go). Some builds also fail due to the API
documentation system being used (epydoc). This is work in progress and
will be fixed by the end of this week.
The idea now--build-wise--is to build the Python3 ports for a
considerable amount of time _only_ against those distro versions, that
are not yet released--thus in testing phase--themselves, that is:
Debian testing Debian unstable
Fedora rawhide openSUSE Factory (I don't see builds for Factory on jenkins.x2go.org, though)
All released distros (Debian (old)stable, Centos 6+7, Fedora XY, etc.)
will receive nightly built packages from the above mentioned release
branches.
Benefits are:
Disadvantages:
Comments? Requests for feedback!
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de