I’m trying to automate the process of installing from source the weekly version of
lsst_distrib at CC-IN2P3. The goal is to have a shared, read-only installation of the most recent weeklies, for which I would like to have a repeatable procedure in place.
Currently I’m facing issues when installing from source following the documentation. I’m currently trying to install the EUPS product
w_2017_5. If I use the master version of newinstall.sh I get an error:
$ curl -OL https://raw.githubusercontent.com/lsst/lsst/master/scripts/newinstall.sh
$ PYTHON=/usr/bin/python bash newinstall.sh -b
LSST Software Stack Builder
(23) Failed writing body
!!! This script differs from the official version on the distribution server.
If this is not intentional, get the current version from here:
Installing EUPS (v2.0.2)... done.
Installing Miniconda2 Python Distribution ...
[ 1/1 ] miniconda2 4.2.12 ...
***** error: from /scratch_ssd/fabio/w.2017.5/EupsBuildDir/Linux64/miniconda2-4.2.12/build.log:
Fetching package metadata .........
.Solving package specifications: .
PackageNotFoundError: Package not found: '' Packages missing in current linux-64 channels:
- fontconfig 2.12.1 0
- glib 2.50.2 0
You can search for packages on anaconda.org with
anaconda search -t conda glib
(and similarly for the other packages)
You may need to install the anaconda-client command line client with
conda install anaconda-client
+ exit -5
If I try
w.2017.5 (here) I get the same error, which seems to be linked to
If I try the version of
newinstall.sh recommended for installing
v12 (here) I don’t see this error. This version of
Now my questions:
- What is the recommended version of
newinstall.sh to use for installing a given weekly? Ideally, my installation process should determine that at runtime so that it can be automated.
- Is there a reproducible way to get an installation of
lsst_distrib (both stable and weekly versions) and its dependencies, in particular miniconda? My experience is that in the current situation, depending when you execute
newinstall.sh you may get a potentially more recent version of miniconda (or EUPS for that matter) than the one used when the weekly was actually tagged. This makes very difficult to reproduce the results of the installation process over time.
Any guidance on how to properly tackle this would be appreciated.