Table of Contents

X2Go Packages for Redhat Enterprise Linux and Derivatives

Do not mix-and-match packages from the official EPEL repository with packages from the X2Go EPEL repository. Due to differing version number schemes, you will definitely run into problems. If you really need to switch between repositories, make sure to uninstall all X2Go packages first.

Select one approach listed here, thus either the official (downstream) EPEL packages repository, or our X2Go EPEL repository and stick to it.

Unreleased versions and unofficial (related to the EPEL project) release packages are only available directly from the X2Go project, follow the instructions in the second section to configure your package manager for this.

Using the Official EPEL Packages Repository

X2Go packages are provided by the Fedora EPEL project for RHEL and derivative distributions (e.g. CentOS and ScientificLinux). See using EPEL for instructions on how to configure the EPEL repository.

The X2Go Project can not provide complete support for these packages. While the current downstream EPEL maintainer is part of the X2Go development team, X2Go developers generally do not have access to the official EPEL repository. Problems are best handled downstream.

Now you can search for X2Go related packages that are now available for your system via yum or dnf, whatever is most appropriate for your system: 

$ yum search x2go

or 

$ dnf search x2go

Congratulations, you are now able to access the X2Go packages. You may continue by installing x2goserver, x2goclient or pyhoca-gui or any other of the available packages.

Adding the X2Go Repository to Your Package System

For unsupported, archived EPEL versions, please refer to EPEL Archives.

Base Installation

Download the .repo file and save it to the correct location: 

wget -O /etc/yum.repos.d/x2go.repo \
 https://packages.x2go.org/epel/x2go.repo

For reference, the file will also be inlined here, with the original information being available on https://packages.x2go.org/epel/x2go.repo:

Customization

Edit this file with your preferred editor. 

$ editor /etc/yum.repos.d/x2go.repo

As a rule of thumb: source-labeled repositories are never needed, unless you want to build packages from source. extras-tagged repositories are always needed.

By default, the release-labeled repository is enabled and the nightly-tagged repository is disabled. If you want to use the unreleased, more up-to-date packages, disable the release-labeled repository and enable the nightly-tagged repository.

To use Saimaa ESR, enable the saimaa-labeled repository and disable the release- or nightly-tagged repositories.

Note that not all of X2Go may be provided for RHEL/EPEL 5/6, as these distributions are very old and therefore more work-intensive to develop for.

If you are behind a proxy, make sure the proxy is defined in /etc/yum.conf. Standard yum repos do not use the same connection mechanisms as RHN channels.

Post-Addition Test

Now you can search for X2Go related packages that are now available for your system via yum or dnf, whatever is appropriate for your system: 

$ yum search x2go

or 

$ dnf search x2go

Congratulations, you are now able to access the X2Go packages. You may continue by installing x2goserver-xsession, x2goclient or pyhoca-gui or any other of the available packages.

Mirroring This Repository

The packages in this repository can be mirrored via rsync: 

rsync -avP packages.x2go.org::epel </dest/path/of/local/mirror/epel>