Skip to content

Conversation

@climbfuji
Copy link
Collaborator

@climbfuji climbfuji commented Dec 31, 2025

Description

All in the title. See #1835 for details

Dependencies

Issues addressed

Part of #1835

Applications affected

None (all deployed and tested as part of the release)

Systems affected

None (all deployed and tested as part of the release)

Testing

  • CI: Note whether the automatic tests (GitHub actions tests that run automatically for every commit) pass or not
    • GitHub actions CI tests pass
    • 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
    • ...

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 spack-stack wiki will be made when this PR is merged

climbfuji and others added 13 commits December 4, 2025 19:02
…fms), update common packages_clang.yaml (ip openmp), update navy-aws site config (JCSDA#1838)

For release/2.0 (will merge back to develop later):
- Bug fix for eckit/libzip in spack-packages, see [release/2.0] Bug fix for eckit: handle new compression backend zip (libzip) for version 1.32+ spack-packages#26
- Add missing -i fms to show_duplicate_packages check in util/nrl/batch_install.sh
- Configs/common/packages_clang.yaml: remove ~openmp variant for package ip
- Update site config for tier-1 platform navy-aws (HSP ParallelWorks AWS)
This is the "simple" solution to JCSDA#1842. The ideal way will be to do so via spack-packages, but since spack-stack 2.0 is out soon, this is the "easy" way.

We can undo this once/if spack/spack-packages#2729 is merged and then get into 2.1
… site config updates round 2 (JCSDA#1844)

- Fix MET segmentation faults (spack-packages submodule, see [release/2.0] Fix MET segfaults (fixup_rpath --> environment modification) spack-packages#29). This requires adding libpython3.* to the whitelist in util/ldd_check.py
- Site config updates for navy-aws tier1 site, add site config to NRL batch install script
…CSDA#1849)

Update batch_install.sh - workaround for ParallelWorks: no NRL GitHub access (yet), turn off adp variant.
In addition to including the site config for the 2.0 release this also includes the py-scipy config change discussed in JCSDA#1848

Finally, the rocky8 config is fairly out of date, I'm removing it for now.
* put NCO-approved pkg list under wcoss2 site config instead of nco template
* acorn deployments.yaml: use @
* allow setup.sh to run from outside of spack-stack dir structure
* update repos/builtin/ submodule
* debug harfbuzz (disable cmake)

---------

Co-authored-by: Dom Heinzeller <dom.heinzeller@icloud.com>
…avy (JCSDA#1852)

Updates for release/2.0 for ParallelWorks Navy: configs/sites/tier1/navy-aws/packages_gcc-13.3.1.yaml, util/nrl/batch_install.sh
* Configuration changes for discover-scu17 for spack-stack 2.0.0
* Update repos/builtin submodule to JCSDA/spack-packages@97141f4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

5 participants