Skip to content

Conversation

@climbfuji
Copy link
Collaborator

@climbfuji climbfuji commented Sep 18, 2025

Description

See title. The common scenario for applying this update on the supported systems, which already have installations of spack-stack-1.9.3 from tag 1.9.3 (hash 58660d3; will be retagged once everything is finalized) is as follows:

# 1. In the spack-stack-1.9.3 directory, run the usual preamble for your system and source setup.sh

# 2. Get latest tag of the spack submodule
cd spack
git remote update
git fetch --tags --force
git checkout spack-stack-1.9.3
git log
cd ..

# 3. Update spack-stack; two options
#   a) PR https://github.com/JCSDA/spack-stack/pull/1778 isn't merged yet

git remote -v show
git remote add dom https://github.com/climbfuji/spack-stack
git remote update
git checkout dom/feature/rel190_crtmfix_addon

#    b) PR https://github.com/JCSDA/spack-stack/pull/1778 was merged and you are on the release/1.9.0 branch locally

git remote update
git pull origin release/1.9.0

# 4. For each unified environment starting with ue- in envs/, do the following (example ue-gcc-11.2.1 on Nautilus):

spack stack create env --name=ue-gcc-11.2.1-crtm-fix-3.1.1.3 --site=nautilus --compiler=gcc --template=unified-dev --upstream=$PWD/envs/ue-gcc-11.2.1/install 2>&1 | tee log.create.ue-gcc-11.2.1-crtm-fix-3.1.1.3.001
spack env activate -p envs/ue-gcc-11.2.1-crtm-fix-3.1.1.3
spack concretize --force --fresh 2>&1 | tee log.concretize.ue-gcc-11.2.1-crtm-fix-3.1.1.3.001

# Verify that there is only one version of [email protected] and that there is no [email protected] in the list of duplicates
./util/show_duplicate_packages.py -d log.concretize.ue-gcc-11.2.1-crtm-fix-3.1.1.3.001

spack install --verbose --no-cache 2>&1 | tee log.install.ue-gcc-11.2.1-crtm-fix-3.1.1.3.001

spack module tcl refresh -y --upstream-modules # replace tcl with lmod as required

spack stack setup-meta-modules

Then, update the release notes for 1.9.3 (see separate list for addon environment installations): #1760

Note that updated the spack-stack wiki release documentation accordingly: https://github.com/JCSDA/spack-stack/wiki/spack%E2%80%90stack%E2%80%901.9.3-release-documentation

Dependencies

None

Issues addressed

Closes JCSDA/spack#565

Applications affected

UFS Global Workflow

Systems affected

All tier-1 platforms

Testing

  • CI: Note whether the automatic tests (GitHub actions tests that run automatically for every commit) pass or not
    • GitHub actions CI tests pass in progress
    • GitHub actions CI tests do not pass (provide explanation)
    • GitHub actions CI tests skipped (provide explanation if necessary)
  • New tests added: List and describe any new tests added to GitHub actions
    • ...
  • Additional testing: Add information on any additional tests conducted
    • Installed the addon environment on Nautilus with GNU following the above instructions

Checklist

  • This PR addresses one issue/problem/enhancement or has a very good reason for not doing so.
  • These changes have been tested on the affected systems and applications.
  • 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 PR
    • For site config updates, check in particular doc/source/PreConfiguredSites.rst and doc/source/MaintainersSection.rst
  • All necessary updates to the spack-stack wiki were made

Copy link
Collaborator

@RatkoVasic-NOAA RatkoVasic-NOAA left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's commit this and use option b)

@climbfuji climbfuji merged commit e5bdcd3 into JCSDA:release/1.9.0 Sep 19, 2025
8 checks passed
@climbfuji climbfuji deleted the feature/rel190_crtmfix_addon branch September 19, 2025 01:38
@climbfuji climbfuji mentioned this pull request Sep 19, 2025
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

No open projects

Development

Successfully merging this pull request may close these issues.

3 participants