Details
-
Type:
Bug
-
Status: Won't Fix
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Stack Documentation and UX
-
Labels:None
-
Epic Link:
-
Team:SQuaRE
Description
Original report:
Installing lsstsw on RHEL6 (and presumably derivatives like Scientific Linux and CentOS) fails because the built-in git client does not have https support. The "git" transport protocol does work and is a suitable alternative.
This is a problem within bin/deploy where versiondb.git and lsst_build.git are cloned (fixed on my machine with replacing https: -> git
.
Similarly, in etc/repos.yaml I had to replace all the https: with git: for the downloads to work.
I am not sure if this is a general solution, however. On Stack Overflow somebody noted that some places block the git: transport protocol. Though I don't know how this can be configured.
This ticket is the result of some confusion over how RHEL6 users should configure their environment. Documentation should be examined to clarify that it is always needed regardless of newinstall vs lsstsw and regardless of whether people know they are using C++11.
Attachments
Issue Links
- mentioned in
-
Page Loading...
No, but apparently somebody did. I just spent too much time looking at this. It seems that lsst-dev grabs the devtoolset-3 from the (free as in beer) channel https://www.softwarecollections.org/repos/rhscl/devtoolset-3/epel-6-x86_64 which includes devtoolset-3-git. Here at SLAC we get the devtoolset-3 from our local mirror of the official (free as in speech, I suppose) RHEL channel, rhel-x86_64-server-6-rhscl, which does not include devtoolset-3-git. Looking at the official Red Hat source download (free as in speech and beer) site: http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/RHSCL/SRPMS/ it also does not include devtoolset-3-git.
Therefore, official redhat customers will need to use the git19 package, while those using clones will not.
I don't know if there are any other missing/extra packages, but boy that is unpleasant.