Replies: 1 comment
-
Hi @jrobbin I think we spoke in Slack and I think the issue in your case was a problem with the SSL certs on the machine. I think the issue was that the download from them mirror failed, and in that case Spack was also trying to download from the original source (which also failed, but sometimes that would succeed if the only issue was the mirror being down). Generally the public mirror should be automatically available. This can be confirmed by doing |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Do I need to tell spack to use the spack-public mirror? I see it's listed ('spack mirror list'), but when I install something, say 'spack install xz', spack still uses the source tarball on sourceforge.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions