Final updates of develop from release 1.9.3

[climbfuji]

Description

Final round of updates from release 1.9.3 (branch release/1.9.0) for develop. An attempt will be made to pull these updatesinto the new feature/update_to_spack_v1 branch for changes that are not related to site configs, and for site configs that haven't been updated yet to work with spack v1. This will be a follow-up PR titled "Update feature/update_to_spack_v1 from develop".

Dependencies

• Waiting on [spack-stack-dev] Add crtm-fix@3.1.1.3 spack#567
• Waiting on Bug fix for wgrib2 from release/1.9.0: support variant netcdf when=@3.6: (#561) spack#568

Issues addressed

Closes #1694
Closes #1760

Applications affected

None (all changes already deployed as part of spack-stack-1.9.3)

Systems affected

None (all changes already deployed as part of spack-stack-1.9.3)

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

[rickgrubin-noaa]

While building wgrib2 this way "works" (see: JCSDA/spack#561), wgrib2/package.py ought to be properly fixed.

[climbfuji]

Good point, see the CI failure: https://github.com/JCSDA/spack-stack/actions/runs/18286538992/job/52062910954

@AlexanderRichert-NOAA @rickgrubin-noaa What is the permanent fix? Will that be made for spack-packages only i.e. do we bring over the temporary fix from the spack submodule release/1.9.0 branch for the time being?

[climbfuji]

@rickgrubin-noaa I've decided to pull in your temporary fix for the reasons stated in JCSDA/spack#568. I assume this hasn't been fixed yet in the new spack-packages repo?

[rickgrubin-noaa]

@rickgrubin-noaa I've decided to pull in your temporary fix for the reasons stated in JCSDA/spack#568. I assume this hasn't been fixed yet in the new spack-packages repo?

This has not been fixed in the new spack-packages repo.

As far as I can tell (and @AlexanderRichert-NOAA certainly understand better than I), the temporary fix implemented for v3.6.0 isn't necessarily applicable for other, earlier versions. I have not looked into it further.