chore: spack-1.1.1#195
Open
wdconinc wants to merge 4 commits into
Open
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
wdconinc
force-pushed
the
spack-1.1.1
branch
2 times, most recently
from
d7ea52d to
afd56b1
Compare
wdconinc
force-pushed
the
spack-1.1.1
branch
2 times, most recently
from
fb9075a to
e5262f1
Compare
veprbl
approved these changes
May 11, 2026
* Initial plan * docs: update SPACK_VERSION example to v1.1.1 in spack-environment.md Co-authored-by: wdconinc <4656391+wdconinc@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: wdconinc <4656391+wdconinc@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Briefly, what does this PR introduce?
This PR upgrades spack to v1.1.1, diff.
In spack v1.1.1, the silent ignoring of libcurl SSL certificate errors in CMake FetchContent operations was fixed and is now an error. In the container build, we are running without access to the CA certificates that sign the re-encrypted MITM SSL pages on US DOE nodes. Thus, this minor bugfix upgrade requires quite a bit more care than is typical.