ESMF 8.7.0

[anton-seaice]

To build access-om3, we need ESMF version 8.7.0

However this was not available in spack release/0.22 - which is the currently preferred version.

I suggest we patch in the changes to esmf package from releases/0.23 into the releases/0.22 branch ? The upstream changes which are newer use some features not available in releases/0.22 (e.g. "virtuals")

This is now causing failures in build-CI , see ACCESS-NRI/access-spack-packages#290

[anton-seaice]

ping @dougiesquire @harshula

[anton-seaice]

See #13 for proposed change

[harshula]

Hi @anton-seaice , Did you try cherry-picking only this commit 5ef9d7e?

[anton-seaice]

We can do this if that's preferred? I haven't tried but we build from the 8.7.0 gitref all the time, so it should be fine

[harshula]

Hi @anton-seaice , When backporting, it's generally safer to only backport what you need. If you want 8.6.1, then consider cherry-picking f8ad915 too. Doing both will avoid a conflict.

spack-access-nri.git$ git cherry-pick f8ad915100e45a6ec823ea6f01ae295c938fba45
[test-v0.22 c1090d30be] esmf: add v8.6.1 (#44229)
 Author: Matt Thompson <matthew.thompson@nasa.gov>
 Date: Fri May 17 04:49:47 2024 -0400
 1 file changed, 1 insertion(+)

spack-access-nri.git$ git cherry-pick 5ef9d7e3ed047fac2f81f957cd41decc27943974
Auto-merging var/spack/repos/builtin/packages/esmf/package.py
[test-v0.22 da186d06fc] esmf: add version 8.7.0 (#46860)
 Author: Ufuk Turunçoğlu <turuncu@ucar.edu>
 Date: Thu Oct 10 19:43:51 2024 -0600
 1 file changed, 1 insertion(+)

[dougiesquire]

I think this can be closed now?

[anton-seaice]

Closed in #13