[X2Go-Dev] X2go on EPEL6 outdated

[Orion Poplawski]

On 02/01/2016 10:11 AM, Mihai Moldovan wrote:
> On 01.02.2016 03:51 PM, Reinhard Tartler wrote:
>> At my new employer, I've convinced our system administrators to give x2go a
>> shot. They noticed that it is included in EPEL6 and installed it on CentOS6
>> workstations. This test went pretty well so far. Unfortunately, that installed
>> version 3.5 of x2go, which as I understand it is not the best impression that we
>> can make. We deployed it with the sqlite back end and I noticed that the
>> cleansessions daemon appears to crash from time to time. This is very annoying
>> in particular given that we reboot our login nodes about once to twice a year
>> and the effects are rather unintuitive to debug. My hope is that x2go 4 is more
>> resilient here (but I admit that I didn't check myself).
>>
>> In any case, I suppose it is in everyone's best interest to prefer a newer
>> version of x2go than currently in EPEL6
>> (cf. https://dl.fedoraproject.org/pub/epel/6/x86_64/repoview/x2goagent.html) -
>> because otherwise, EPEL user are not going to receive any work towards getting
>> bugfixes.
>
> You're confusing nx-libs, which has a 3.5.x versioning scheme, with the
> x2goserver versioning scheme.
>
> x2goagent is part of nx-libs and 3.5.0.32 is the newest stable release I made.
>
> Likewise, the x2goserver in the EPEL 6 repository is at version 4.0.1.19, which
> is the newest stable version available. 4.1.0.0 is currently on the master
> branch and only available via nightly builds. Nightly builds are not included in
> the official EPEL repository, but can be installed through our repository at
> packages.x2go.org[0]. Please never, ever, mix x2go packages from the official
> repository with these in our repository. Also never, ever, try to "upgrade" from
> one to another. This a recipe for disaster.
>
> Mike#1 suggested making another regular x2goserver release from the stable
> branch, then forking that off as the new LTS version and promoting 4.1.0.0 as
> the new stable branch. I haven't done that, though, because making another LTS
> release does affect pretty much all the other packages we ship, too, and I'm
> fuzzy on the details of what should be considered an LTS-supported platform and
> what not.
>
> Orion, the Fedora developer backporting our packages to EPEL and relaying bug
> reports to the upstream bug tracker is doing a great job at managing and
> updating these packages.

Thank you :).

> The only exception to freshness I could find in the official EPEL 6 repository
> is x2goclient - even though we are currently at 4.0.5.0, the client version
> there is 4.0.1.4.

This is limited by libssh - we have libssh 0.5.5 in EPEL6, but 
x2goclient 4.0.5.0 requires libssh 0.6.1+.


-- 
Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA, Boulder/CoRA Office             FAX: 303-415-9702
3380 Mitchell Lane                       orion at nwra.com
Boulder, CO 80301                   http://www.nwra.com