[X2Go-Dev] Strategy for introducing Python3 ports of PyHoca and X2Go Broker

Mike Gabriel mike.gabriel at das-netzwerkteam.de
Mon Oct 9 11:11:49 CEST 2017


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/release/0.5.0.x

   PyHoca-CLI: release/0.5.0.x
    
https://code.x2go.org/gitweb?p=pyhoca-cli.git;a=shortlog;h=refs/heads/release/0.5.0.x

   X2Go Session Broker: release/0.0.3.x
    
https://code.x2go.org/gitweb?p=x2gobroker.git;a=shortlog;h=refs/heads/release/0.0.3.x

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:

   - master branches and release branches can be tested via nightly builds
   - no dodgy backporting and lack of maintenance for python dependencies
     (see: http://packages.x2go.org/debian/pool/main/p/)
   - stable distro releases will not receive flawed code (the Python3
     port cannot be considered as stable at all, I continuously find more
     issues popping up while testing)

Disadvantages:

   - nightly builds don't build the same Git branches anymore. What you
     find in the nightly built package repo (aka heuler) depends on your
     Linux distro and version

Comments? Requests for feedback!

Thanks!
Mike
-- 

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 at das-netzwerkteam.de, http://das-netzwerkteam.de

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 851 bytes
Desc: Digitale PGP-Signatur
URL: <http://lists.x2go.org/pipermail/x2go-dev/attachments/20171009/6e417557/attachment.sig>


More information about the x2go-dev mailing list