Fedora 20-21 RPM installation

Please note, fedora 20-21 are no longer supported as of 2018-04-21. Packages are currently still available from the ESO repositories, but will no longer be updated, and may disappear at any moment.

If you have not already done so please follow the instructions to configure the ESO RPM repository here -- note if you have already installed ESO pipelines via RPM, then you probably already have the ESO repository configured and enabled.

You can test that it is working with the following command:

yum search eso-

Then to install a package:

sudo yum install <package_name>

Fedora 22-27 RPM installation

Please note, fedora 22-23, fedora 24-25, fedora 26-27 and fedora 28-32 are no longer supported as of 2018-04, 2020-05, 2021-05 and 2022-05 respectively. Packages are still available from the ESO repositories for some of these distributions, but will no longer be updated, and may disappear at any moment -- notably the fedora 24-27 repositories are empty.

If you have not already done so please follow the instructions to configure the ESO RPM repository here -- note if you have already installed ESO pipelines via RPM, then you probably already have the ESO repository configured and enabled.

You can test that it is working with the following command:

dnf search eso-

Then to install a package:

sudo dnf install <package_name>

Fedora 33-35 RPM installation

If you have not already done so please follow the instructions to configure the ESO RPM repository here -- note if you have already installed ESO pipelines via RPM, then you probably already have the ESO repository configured and enabled.

You can test that it is working with the following command:

dnf search eso-

Then to install a package:

sudo dnf install <package_name>

Scientific Linux 7 RPM installation

If you have not already done so please follow the instructions to configure the ESO RPM repository here -- note if you have already installed ESO pipelines via RPM, then you probably already have the ESO repository configured and enabled.

You can test that it is working with the following command:

yum search eso-

Then to install a package:

sudo yum install <package_name>

Fedora 26 & 27 RPM installation

It is possible to use the Fedora 25 RPMs on Fedora 26 & 27 systems. But please note: As the packages were not built natively for this system, there is a possibility of problems due to incompatibility, but thus far tests have been positive.

You will need to enable the Fedora 25 ESO repository. Please follow the instructions below. Please note that you will then be using packages built on Fedora 25 systems. All of our tests thus far show that these binaries behave normally, but there is always the possibility at something behaves peculilarly, or that at some point the packages even simply stop working (due to broken dependancies). Please contact us at support.eso.org if you experience or detect any peculiar behaviour or problems with using the Fedora 25 packages on Fedora 26+ systems. Please note that this method will also give you access to the ESO pipelines via RPM installation. The same message applies: use with caution!

Please copy and paste the following instructions to install and configure the Fedora 25 ESO repository (please copy and paste the lines starting with sudo one at a time):

bash
cd /tmp
wget -O esorepo-fedora25.repo https://ftp.eso.org/pub/dfs/pipelines/repositories/stable/fedora/esorepo.repo
sed -i -e 's/esorepo/esorepo-fedora25/' esorepo-fedora25.repo
sed -i -e 's/enabled=1/enabled=0/' esorepo-fedora25.repo
sed -i -e 's/$releasever/25/' esorepo-fedora25.repo
sudo dnf config-manager --add-repo esorepo-fedora25.repo
exit

You can test that it is working with the following command:

dnf search --enablerepo=esorepo-fedora25 eso-

Then to install a package:

sudo dnf install --enablerepo=esorepo-fedora25 <package_name>

CentOS-7 RPM installation

If you have not already done so please follow the instructions to configure the ESO RPM repository here -- note if you have already installed ESO pipelines via RPM, then you probably already have the ESO repository configured and enabled.

You can test that it is working with the following command:

yum search eso-

Then to install a package:

sudo yum install <package_name>

RedHat Enterprise Linux 7 RPM installation

It is possible to use the Scientific Linux 7 RPMs on RedHat Enterprise Linux 7 systems. But please note: As the packages were not built natively for this system, there is a possibility of problems due to incompatibility, but thus far tests have been positive.

You will need to enable the Scientific Linux 7 ESO repository. Please follow the instructions below. Please note that you will then be using packages built on Scientific Linux 7 systems. All of our tests thus far show that these binaries behave normally, but there is always the possibility at something behaves peculilarly, or that at some point the packages even simply stop working (due to broken dependancies). Please contact us at support.eso.org if you experience or detect any peculiar behaviour or problems with using the Scientific Linux 7 packages on centoOS 7 or RHEL 7 systems. Please note that this method will also give you access to the ESO pipelines via RPM installation. The same message applies: use with caution!

Please copy and paste the following instructions to install and configure the Scientific Linux 7 ESO repository (please copy and paste the lines starting with sudo one at a time):

bash
cd /tmp
wget -O esorepo-sl7.repo https://ftp.eso.org/pub/dfs/pipelines/repositories/stable/sl/esorepo.repo
sed -i -e 's/esorepo/esorepo-sl7/' esorepo-sl7.repo
sed -i -e 's/enabled=1/enabled=0/' esorepo-sl7.repo
sed -i -e 's/$releasever/7/' esorepo-sl7.repo
sudo yum-config-manager --add-repo esorepo-sl7.repo
exit

You can test that it is working with the following command:

yum search --enablerepo=esorepo-sl7 eso-

Then to install a package:

sudo yum install --enablerepo=esorepo-sl7 <package_name>

Ubuntu APT installation

We are also offering Ubuntu repositories on a best-effort-support basis. Ubuntu repositories are currently available for Ubuntu 64bit 16.04 LTS, 18.04 LTS, 20.04 LTS and 22.04 LTS.

Ubuntu 21.04 & 21.10 repositories are still available but are no longer being updated. They were last updated for P106 (i.e. in Oct 2021). Some of the packages there may still be useful, but are officially are out-of-date and will NOT be updated.

Ubuntu 19.04 & 19.10 repositories are still available but are no longer being updated. They were last updated for P104 (i.e. in Oct 2020). Some of the packages there may still be useful, but are officially are out-of-date and will NOT be updated.

Ubuntu 17.04, 17.10, 18.10 repositories are still available but are no longer being updated. They were last updated for P102 (i.e. in July 2018). Some of the packages there may still be useful, but are officially are out-of-date and will NOT be updated.

Ubuntu 12 LTS and 14.04 LTS repositories are still available but are no longer being updated. They were last updated for P101 (i.e. in December 2017). Some of the packages there may still be useful, but are officially are out-of-date and will NOT be updated. In particular the Skycat provided by the FIMS package will not be able to connect to the ESO image and catalogue servers.

• if you experience any problems
• if your version of Ubuntu is not supported
• especially if you appreciate this service and would like to see it continued and (eventually) expanded (as this will help us to motivate commiting resources to doing so...)

Please also note that Ubuntu USD-ESO repository support is (currently) only available for Phase 2 preparation tool software, the ESO pipelines are not currently available from ESO for Ubuntu (though appear to be via the community at large).

Please copy and paste the following instructions to install and configure the Ubuntu USD-ESO repository (please copy and paste the lines starting with sudo one at a time). The following assumes your SHELL is bash, if in doubt:

bash

First install the security key. For versions lower than 21:

wget -qO - https://ftp.eso.org/pub/usg/ubuntu/dists/keyFile | sudo apt-key add -

For versions equal to and above than 21:

wget -qO - https://ftp.eso.org/pub/usg/ubuntu/dists/keyFile \
| gpg --dearmor \
| sudo tee /usr/share/keyrings/eso-ubuntu-repo-archive-keyring.gpg >/dev/null


Then install the repository:

sudo add-apt-repository "deb https://ftp.eso.org/pub/usg/ubuntu $(lsb_release -sc) universe"

For versions equal to and above than 21, installing the repository will result in an error, something like the following:

W: GPG error: https://ftp.eso.org/pub/usg/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 320206063753CDCB
E: The repository 'https://ftp.eso.org/pub/usg/ubuntu jammy InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.


So for versions equal to and above than 21, the following additional step is required:

sudo sed -i \
-e 's@deb http@deb [] http@' \
-e 's@\]@ signed-by=/usr/share/keyrings/eso-ubuntu-repo-archive-keyring.gpg]@' \
-e 's@\[ signed@[signed@' \
/etc/apt/sources.list.d/archive_uri-https_ftp_eso_org_pub_usg_ubuntu-*.list


You can test that it is working with the following command:

sudo apt update
sudo apt-cache search eso-

You should see (amongst others) the eso-fors-fims package

Then to install a package:

sudo apt-get install <package_name>

Note, to properly install the eso-fors-fims package you will also need to install the eso-qfits package, i.e.:

sudo apt install eso-qfits eso-fors-fims

And you will need to use the following command to successfully run fims.

LD_LIBRARY_PATH=/usr/lib64 fims.sh <camera = R or B>

Note, on most (recent) Debian-based systems, the default shell is dash, and as a result /usr/bin/sh is a softlink to dash. This causes the skycat script to mal-function (though skycat still opens). You can reconfigure the default shell to bash with:

sudo dpkg-reconfigure dash

Answer no, and the default shell will be set to bash, including softlinking /usr/bin/sh to bash.

Note, skycat is incompatible with certain Window Server options, 'GNOME Classic' is OK, but GNOME (which uses weyland) causes problems.

For the technically minded: The Ubuntu packages are created from Fedora RPMs using alien.

other Debian with APT (e.g. Mint)

We are also offering Ubuntu repositories on a best-effort-support basis. Ubuntu repositories are currently available for Ubuntu 64bit 16.04 LTS, 18.04 LTS, 20.04 LTS and 22.04 LTS.

Ubuntu 21.04 & 21.10 repositories are still available but are no longer being updated. They were last updated for P106 (i.e. in Oct 2021). Some of the packages there may still be useful, but are officially are out-of-date and will NOT be updated.

Ubuntu 19.04 & 19.10 repositories are still available but are no longer being updated. They were last updated for P104 (i.e. in Oct 2020). Some of the packages there may still be useful, but are officially are out-of-date and will NOT be updated.

Ubuntu 17.04, 17.10 & 18.10 repositories are still available but are no longer being updated. They were last updated for P102 (i.e. in July 2018). Some of the packages there may still be useful, but are officially are out-of-date and will NOT be updated.

Ubuntu 12 LTS and 14.04 LTS repositories are still available but are no longer being updated. They were last updated for P101 (i.e. in December 2017). Some of the packages there may still be useful, but are officially are out-of-date and will NOT be updated. In particular the Skycat provided by the FIMS package will not be able to connect to the ESO image and catalogue servers.

These Ubuntu repositories can also be used by (some) other Debian systems with the APT package management system, especially if they are derived from Ubuntu, e.g. Linux Mint. You just have to work out which of our Ubuntu repositories best matches your system, for example Linux Mint 18 & 18.* are based on Ubuntu 16.04 (code name xenial) while Linux Mint 17 & 17.* are based on Ubuntu 14.04 (code name trusty). For example see this page for Linux Mint version information, and this page for Ubuntu code names (the codename to use is the first name in the Code name column all in lowercase).

If you use our Ubuntu repositories, please consider providing feedback to support.eso.org:

• if you experience any problems
• if your version of Ubuntu is not supported
• especially if you appreciate this service and would like to see it continued and (eventually) expanded (as this will help us to motivate commiting resources to doing so...)

Please also note that Ubuntu USD-ESO repository support is (currently) only available Phase 2 preparation tool software, the ESO pipelines are not currently available from ESO for Ubuntu (though appear to be via the community at large).

Please copy and paste the following instructions to install and configure the Ubuntu USD-ESO repository (please copy and paste the lines starting with sudo one at a time). The following assumes your SHELL is bash, if in doubt:

bash

First install the security key. For versions lower than the equivalent of Ubuntu-21:

wget -qO - https://ftp.eso.org/pub/usg/ubuntu/dists/keyFile | sudo apt-key add -

For versions equal to and above the equivalent of Ubuntu-21:

wget -qO - https://ftp.eso.org/pub/usg/ubuntu/dists/keyFile \
| gpg --dearmor \
| sudo tee /usr/share/keyrings/eso-ubuntu-repo-archive-keyring.gpg >/dev/null


Then install the repository:

sudo add-apt-repository "deb https://ftp.eso.org/pub/usg/ubuntu <ubuntu_release_codename> universe"

where you will have to enter manually the <ubuntu_release_codename> most appropriate for your system. Check this wikipedia page for ubuntu releases, the release code name to use is the first word of the Official Code name, all in lower case, e.g. 18.04 LTS --> 'bionic', 20.04 LTS --> 'focal', 22.04 LTS --> 'jammy'.

For versions equal to and above the equivalent of Ubuntu-21, installing the repository will result in an error, something like the following:

W: GPG error: https://ftp.eso.org/pub/usg/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 320206063753CDCB
E: The repository 'https://ftp.eso.org/pub/usg/ubuntu jammy InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.


So for versions equal to and above than 21, the following additional step is required:

sudo sed -i \
-e 's@deb http@deb [] http@' \
-e 's@\]@ signed-by=/usr/share/keyrings/eso-ubuntu-repo-archive-keyring.gpg]@' \
-e 's@\[ signed@[signed@' \
/etc/apt/sources.list.d/archive_uri-https_ftp_eso_org_pub_usg_ubuntu-*.list


You can test that it is working with the following command:

sudo apt update
sudo apt-cache search eso-

You should see (amongst others) the eso-fors-fims package

Then to install a package:

sudo apt-get install <package_name>

Note, to properly install the eso-fors-fims package you will also need to install the eso-qfits package, i.e.:

sudo apt install eso-qfits eso-fors-fims

And you will need to use the following command to successfully run fims.

LD_LIBRARY_PATH=/usr/lib64 fims.sh <camera = R or B>

Note, on most (recent) Debian-based systems, the default shell is dash, and as a result /usr/bin/sh is a softlink to dash. This causes the skycat script to mal-function (though skycat still opens). You can reconfigure the default shell to bash with:

sudo dpkg-reconfigure dash

Answer no, and the default shell will be set to bash, including softlinking /usr/bin/sh to bash.

Note, skycat is incompatible with certain Window Server options, 'GNOME Classic' is OK, but GNOME (which uses weyland) causes problems.

For the technically minded: The Ubuntu packages are created from Fedora RPMs using alien.

Generic RPM-Linux systems and Source-RPMs

As an example, here's how to build skycat on a Fedora38 system from the Fedora37 SRPM.

sudo dnf install rpm-build
rpm -ivh https://ftp.eso.org/pub/dfs/pipelines/repositories/stable/fedora/37/src/eso-skycat/eso-skycat-3.1.6-1.fc37.src.rpm
sudo dnf builddep rpmbuild/SPECS/eso-skycat.spec
rpmbuild -ba rpmbuild/SPECS/eso-skycat.spec
sudo dnf install rpmbuild/RPMS/*/eso-skycat-3.1.6-1.fc38.*.rpm

Mac OS X/OS X/macOS

ESO has chosen to use MacPorts for software distribution and has thus setup an official ESO MacPorts repository.

Macports depends on Xcode and the Xcode Command line tools, see the MacPorts installation guide.

The ESO MacPorts repository currently provides BINARY packages for Mac OS X 10.11 to 10.15, though not all packages are available for all OS versions. For earlier and more recent OS versions than currently supported, using the ESO MacPorts repository is still supported for most software packages, it just means that ESO packages will be built natively on your machine from SOURCE, which in most cases just means it will take longer to install a given package than required for the BINARY packages, but it should eventually get there. Some packages however are known not to work on certain Mac OS versions, and in that case even the SOURCE installation will fail, or else it is possible the installation itself will apparently succeed, but the sotware may fail to work correctly -- use at your own risk.

Once you have an up and running Macports system, please follow the procedure described in bullet point 1 here to configure the ESO MacPorts repository.

If you haven't done so within the past two weeks it is probably a good idea to also do

sudo port selfupdate
sudo port upgrade outdated

Once the ESO MacPorts repository is installed via the instructions above you can browse the avaiable (non pipeline) ESO packages with:

port search eso-

Then to install a package:

sudo port install <package_name>