[spack v0.23 / spack-stack v1] Add esmf@8.9.1#571
Merged
climbfuji merged 1 commit intoJCSDA:spack-stack-devfrom Nov 21, 2025
Merged
[spack v0.23 / spack-stack v1] Add esmf@8.9.1#571climbfuji merged 1 commit intoJCSDA:spack-stack-devfrom
climbfuji merged 1 commit intoJCSDA:spack-stack-devfrom
Conversation
11 tasks
areinecke
approved these changes
Nov 20, 2025
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.
Description
Add esmf@8.9.1.
A similar change already went into the feature/update_to_spack_v1 branches, but it turns out we need it in develop now.
I will resolve merge conflicts when I pull the updated spack-stack develop / spack spack-stack-dev branches into the feature/update_to_spack_v1 branches.
Testing
spack-stack PR JCSDA/spack-stack#1824
Note that the spack CI windows audit test is expected to fail; it did so ever since spack upstream updated to spack v1.