I’m interested in trying a build of the (future) release candidate to be distributed via CernVM FS. If there is some (even preliminary) documentation on how to build and test the release I’m happy to try it and provide feedback. Alternatively, if you plan to centrally produce a binary release distributable via CernVM FS I would be happy to help with that also.
My goal is that the CernVM FS binaries of the future release be available when the new release is officially announced.
creates a file named 8g2 and not newinstall.sh as I think is intended. I did instead:
curl -o newinstall.sh -L http://ls.st/8g2
In addition, executing newinstall.sh shows the warning below:
$ source newinstall.sh
LSST Software Stack Builder
=======================================================================
!!! This script differs from the official version on the distribution server.
If this is not intentional, get the current version from here:
http://sw.lsstcorp.org/eupspkg/newinstall.sh
<...>
The file in http://sw.lsstcorp.org/eupspkg/newinstall.sh is actually an older version of the one in http://ls.st/8g2.
Finally, I encountered an issue when building v12.0 on OS X Yosemite. The problem seems to be related to the package afw. Here is the trace:
$ eups distrib install -t v12_0 lsst_apps
<...>
[ 39/62 ] pex_config 12.0 done.
[ 40/62 ] afw 12.0 ...
***** error: from /cvmfs/lsst.in2p3.fr/software/darwin-x86_64/lsst-v12.0/EupsBuildDir/DarwinX86/afw-12.0/build.log:
The errors for vector batch interpolation with variance
worst mu error 1.30094019438e-05
worst sig2 error 2.09062343838e-07
The errors for vector batch interpolation without variance
worst mu error 1.30094019438e-05
The errors for vector add interpolation
worst mu error 0.000142775502779
worst sig2 error 3.84439639196e-07
The following tests failed:
/cvmfs/lsst.in2p3.fr/software/darwin-x86_64/lsst-v12.0/EupsBuildDir/DarwinX86/afw-12.0/afw-12.0/tests/.tests/testGaussianProcess.py.failed
1 tests failed
scons: *** [checkTestStatus] Error 1
scons: building terminated because of errors.
+ exit -4
eups distrib: Failed to build afw-12.0.eupspkg: Command:
source /cvmfs/lsst.in2p3.fr/software/darwin-x86_64/lsst-v12.0/eups/bin/setups.sh; export EUPS_PATH=/cvmfs/lsst.in2p3.fr/software/darwin-x86_64/lsst-v12.0; (/cvmfs/lsst.in2p3.fr/software/darwin-x86_64/lsst-v12.0/EupsBuildDir/DarwinX86/afw-12.0/build.sh) >> /cvmfs/lsst.in2p3.fr/software/darwin-x86_64/lsst-v12.0/EupsBuildDir/DarwinX86/afw-12.0/build.log 2>&1 4>/cvmfs/lsst.in2p3.fr/software/darwin-x86_64/lsst-v12.0/EupsBuildDir/DarwinX86/afw-12.0/build.msg
exited with code 252
I tried also to build using export MACOSX_DEPLOYMENT_TARGET="10.9" and it fails also building afw, but the error message is different. I can provide it if that may help.
Ouch, sorry! That’s what I get for trying to put in a last minute update. I’ll switch to using the full URL and drop the short links. Fixing the doc now.
We’re switching to GitHub for distributing newinstall.sh since it reduces overhead in distributing updated newinstall.sh scripts.
Hi @jsick et al. (& thanks for putting this together!).
Quick feedback – The instructions on how to run the comparison after the demo seem out of date. Running ./bin/compare detected-sources.txt worked for me.
There is still an issue. The updated version of the documentation suggests to use curl -OL https://raw.githubusercontent.com/lsst/lsst/v12/scripts/newinstall.sh but this does not work either:
Seems that the tagging format got changed when v12 was re-tagged. @frossie, do you know why the tag got changed from v12 to 12.0? Are we settled on this format for branch/tag names for releases?
Yes, it was my bad for not initially checking cURL against the short link. I did check the first patch. Then the tag got switched to a release branch with a different name afterwards, and now I’ve tested the latest patch. Hopefully that clarifies what happened.
Once we’ve got a system these sorts of documentation changes will all be automated from single origins of truth.
