Update Ursa site config for building spack-stack develop 2025/10/02 unified environments #1787
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
Update configs/sites/tier1/ursa/compilers.yaml and configs/sites/tier1/ursa/packages_oneapi.yaml for building unified environment on Ursa for spack-stack develop as of 2025/10/02.
Tested on Ursa, environments built cleanly for both compilers.
Note that the Ursa site config will be updated shortly again on the feature/update_to_spack_v1 branch, this will likely include reverting back to external compiler runtime libraries.
Dependencies
None
Issues addressed
None. Related to automation work (see #1788).
Applications affected
None
Systems affected
Ursa
Testing
Checklist
All dependency PRs/issues have been resolved and this PR can be merged.All necessary updates to the documentation on readthedocs are included in this PRdoc/source/PreConfiguredSites.rst
anddoc/source/MaintainersSection.rst
All necessary updates to the spack-stack wiki will be made when this PR is merged