Update met and metplus new versions.

[RatkoVasic-NOAA]

Update met and metplus package.py files.

[climbfuji]

does this build with the release/1.0.0 branch of spack-stack?

[RatkoVasic-NOAA]

does this build with the release/1.0.0 branch of spack-stack?

Did I miss something?

[RatkoVasic-NOAA]

does this build with the release/1.0.0 branch of spack-stack?

OK, maybe you meant 2.0.0 :-) IDK, probably. I build only with 1.9.0 (tag 1.9.2).

[climbfuji]

You just answered. Ok, if spack-stack release/1.9.0 works with this branch (I was worried about the new language dependencies), then ok.

[RatkoVasic-NOAA]

I'll correct myself. I tested with old package.py's, just with added new versions for met and metplus. I just added new changes which are currently in develop. I will test with new package.py's before I create PR for spack-stack/1.9.0

[RatkoVasic-NOAA]

@climbfuji tested, all OK.

[climbfuji]

Perfect, thanks! I'll merge this, then I can tag spack and take care of the submodule pointer update in spack-stack in my currently open draft PR.

Just to confirm, these are additional versions that do not replace the default met/metplus versions, correct? In other words, they will go into an addon environment?

[RatkoVasic-NOAA]

Just to confirm, these are additional versions that do not replace the default met/metplus versions, correct? In other words, they will go into an addon environment?

No addons, they will replace old versions. Nobody is using old ones.
So, if you are going to update pointer to spack, then I'll just create PR for spack-stack configs/common/packages.yaml file.

[RatkoVasic-NOAA]

@climbfuji actually, you don't need to update spack pointer, I just did that. My spack-stack PR is ready.

[climbfuji]

I don't see the PR yet?

[RatkoVasic-NOAA]

I'm finishing description.