Update spack-packages from spack-packages/develop 2026/06/04#67
Merged
climbfuji merged 3709 commits intoJun 24, 2026
Merged
Conversation
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
This PR pulls in the upstream spack-packages develop branch as of 2026/06/04.
Additional changes:
py-pybtex, see Update dependencies for py-pybtex spack/spack-packages#5141 for the upstream PRpy-lxml, see py-lxml@5: flags to compile with gcc@14 / oneapi@2026 spack/spack-packages#5307 for the upstream PRPackages with merge conflicts that should be examined by the reviewers (all others were straightforward):
Note that we have to keep using the old installer, because some packages simply don't build with the new one.
Testing and Issues
See JCSDA/spack-stack#2039