Update spack-packages for libpng, ncurses, openblas, py_matplotlib

[mathomp4]

Description

This is a spack-stack PR to test the package updates in JCSDA/spack-packages#63

Dependencies

None

Issues addressed

Related to:

• Fixes [INSTALL]: openblas 0.3.32 #2022
• Fixes [INSTALL]: libpng 1.6.55 #2021
• Fixes [INSTALL]: py-matplotlib 3.10.8 #2020
• Fixes [INSTALL]: git-lfs 3.7.1 #1881

and partially:

• Feature request: xesmf and cmocean #1502

I'm not using the "Closes" here since, well, nothing actually update the yaml configs to these yet.

Applications affected

Anything using libpng, ncurses, openblas, py_matplotlib, git-lfs

Systems affected

All

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

[mathomp4]

Huh. I seem to have gsi-ncdiag updates as well? I don't remember updating that.

I think I'm capturing a bit of #1992 from @AlexanderRichert-NOAA

[climbfuji]

I merged #1992 and unfortunately you need resolve the "conflict" in your spack-stack PR. Just pull in develop, make sure you are still pointing to your spack-packages branch (which should be up to date with spack-stack-dev), then resolve the conflict by running git add repos/builtin and git commit.

[mathomp4]

I merged #1992 and unfortunately you need resolve the "conflict" in your spack-stack PR. Just pull in develop, make sure you are still pointing to your spack-packages branch (which should be up to date with spack-stack-dev), then resolve the conflict by running git add repos/builtin and git commit.

I think I did it right...

[climbfuji]

@mathomp4 I merged the spack-packages PR. New hash is JCSDA/spack-packages@6fd08ef

[mathomp4]

@climbfuji I think I did it right. git submodules combined with remotes and forks still confuses me...

[climbfuji]

Thanks!