Skip to content
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

Closed
jrk opened this issue Jul 31, 2015 · 8 comments
Closed

Comments

@jrk
Copy link

jrk commented Jul 31, 2015

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:

curl: (77) error setting certificate verify locations:

It seems this occurs because (1) anaconda/bin is prepended to the $PATH, and (2) anaconda includes its own anaconda/bin/curl which then takes over subsequent curl 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.

@jhoblitt
Copy link
Member

@jrk Thanks for reporting this. We probably can't hardcode the curl path because of OSX. We might be able to change the PATH ordering so that anaconda binaries don't override what's supplied by the system.

@jrk
Copy link
Author

jrk commented Jul 31, 2015

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 CURL=$(which curl) at the start, before the PATH is extended.

@jhoblitt
Copy link
Member

I'm not sure if anaconda needs to be in the search path at all -- I'll do some testing in the morning.

@mjuric
Copy link
Member

mjuric commented Jul 31, 2015

@jrk @jhoblitt I'll open an issue with the Continuum guys.

In the meantime, I think you can add conda remove curl right after Anaconda gets installed (it's not needed, since the system already has it).

@mjuric
Copy link
Member

mjuric commented Jul 31, 2015

Btw., I have a PR almost ready to replace Anaconda with Miniconda (I think it doesn't pull in curl by default).

@mjuric
Copy link
Member

mjuric commented Jul 31, 2015

FYI, this is the upstream issue -- https://github.com/conda/conda-recipes/issues/352..

@timj
Copy link
Member

timj commented Sep 15, 2016

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???

@jrk
Copy link
Author

jrk commented Sep 15, 2016

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
wrote:

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???


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#40 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAju9EYcKpMrKY6yosKUPX9w5NH2ZUKks5qqarxgaJpZM4FjNaU
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants