Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-7564

Update docs to clarify that RHEL6 users always need devtoolset-3

    XMLWordPrintable

    Details

      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

            Activity

            Hide
            erykoff Eli Rykoff added a comment -

            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.

            Show
            erykoff Eli Rykoff added a comment - 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.
            Hide
            jhoblitt Joshua Hoblitt added a comment -

            Jonathan Sick Is this issue still valid as we've since migrated to devtoolset-6?

            Show
            jhoblitt Joshua Hoblitt added a comment - Jonathan Sick Is this issue still valid as we've since migrated to devtoolset-6 ?
            Hide
            erykoff Eli Rykoff added a comment -

            Same issue with devtoolset-6 which I have access to at SLAC.  That is, I need to do scl enable devtoolset-6 git19 tcsh in order to access the new/correct version of git.

            Show
            erykoff Eli Rykoff added a comment - Same issue with devtoolset-6 which I have access to at SLAC.  That is, I need to do scl enable devtoolset-6 git19 tcsh in order to access the new/correct version of git.
            Hide
            tjenness Tim Jenness added a comment -

            we have:

            https://developer.lsst.io/build-ci/platforms.html

            and

            https://developer.lsst.io/coding/cpp_style_guide.html#we-are-writing-c-14

            in the dev guide but the pipelines install docs are still at v14.0 standard (https://pipelines.lsst.io/install/prereqs/centos.html?highlight=devtoolset) so don't mention devtoolset-6 (we need a "beta" version of those pages and I think that's another ticket somewhere.

            Show
            tjenness Tim Jenness added a comment - we have: https://developer.lsst.io/build-ci/platforms.html and https://developer.lsst.io/coding/cpp_style_guide.html#we-are-writing-c-14 in the dev guide but the pipelines install docs are still at v14.0 standard ( https://pipelines.lsst.io/install/prereqs/centos.html?highlight=devtoolset ) so don't mention devtoolset-6 (we need a "beta" version of those pages and I think that's another ticket somewhere.
            Hide
            tjenness Tim Jenness added a comment -

            Closing this since devtoolset is no longer needed.

            Show
            tjenness Tim Jenness added a comment - Closing this since devtoolset is no longer needed.

              People

              Assignee:
              jsick Jonathan Sick
              Reporter:
              erykoff Eli Rykoff
              Watchers:
              Eli Rykoff, Jim Bosch, John Swinbank, Jonathan Sick, Joshua Hoblitt, Tim Jenness
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.