No more local spack packages in Radiuss Spack Configs#358
Merged
Conversation
adrienbernede
changed the title
adrienbernede
requested review from
adayton1 and
Copilot
and removed request for
Copilot
adayton1
approved these changes
Feb 11, 2026
liu15
approved these changes
Feb 11, 2026
Member
Author
|
@adayton1 you may merge this PR ;) |
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
3 participants
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.
This PR updates Radiuss Spack Configs to the latest release that removed every local changes to the spack packages.
When an update of the Spack packages is needed, it should be pushed directly to spack/spack-packages.
The structure remains in place to test changes to the local packages, but that's for temporary testing only. PRs with local packages will not be merged in Radiuss Spack Configs anymore.
Spack was also updated to v1.1.0.