Set the spack-version explicitly when @git.<gitref> is used for specs#107
Merged
Set the spack-version explicitly when @git.<gitref> is used for specs#107
Conversation
* Spack upstream is planning to insert a spack-version when one is not explicitly provided. * The error we saw when using `spack config change` can be avoided when a spack-version is explicitly provided. * The latest spack-packages repository contains changes that this change requires.
Contributor
|
🚀 Attempted to deploy 🖥️
|
Contributor
|
The model version in the
|
Contributor
|
🚀 Attempted to deploy 🖥️
|
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.
🚀 The latest prerelease
access-om2/pr107-2at f6af9c6 is here: #107 (comment) 🚀