-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
curl installed by anaconda fails to fetch https URLs during later deploy steps #40
Comments
@jrk Thanks for reporting this. We probably can't hardcode the curl path because of OSX. We might be able to change the |
Hard-coding the path definitely seems wrong (why I didn't send a pull request yet), though OS X does also use /usr/bin/curl as its system default. That said, I think you could potentially do something like |
I'm not sure if anaconda needs to be in the search path at all -- I'll do some testing in the morning. |
Btw., I have a PR almost ready to replace Anaconda with Miniconda (I think it doesn't pull in |
FYI, this is the upstream issue -- https://github.com/conda/conda-recipes/issues/352.. |
Can this issue be closed now that we use miniconda? Also, that upstream issue is no longer accessible. Did all the issues associated with conda-recipes get deleted??? |
I haven't been using this for a while, so for my sake, at least: certainly. On Thu, Sep 15, 2016 at 1:30 PM, Tim Jenness notifications@github.com
|
Following the directions from https://confluence.lsstcorp.org/display/LDMDG/The+LSST+Software+Build+Tool on a fairly vanilla Ubuntu 14.04/x86_64 machine,
deploy
completes its first major step of installing anaconda then immediately fails trying to fetch the git source with a variant of this error:It seems this occurs because (1)
anaconda/bin
is prepended to the$PATH
, and (2) anaconda includes its ownanaconda/bin/curl
which then takes over subsequentcurl
invocations in the deploy script. This seems to be misconfigured by default for SSL, causing the error (apparently looking for CA data in a nonexistent path).The obvious workaround (without disabling SSL certificate validation) is simply to force use of the system
curl
by capturing its path at script startup. stanford-gfx/lsstsw@d95aae6b22 hacks this in for common configurations by hard-coding use of/usr/bin/curl
.The text was updated successfully, but these errors were encountered: