xcdat: [Bug]: 0.2.0 appears to be latest conda-forge release installed on arm64/windows

What happened?

(xcdat031spy532) ml-9953350:ESGFReports duro$ mamba create --dry-run -n xc030spy532mat352 -c conda-forge xcdat

              __    __    __    __
             /  \  /  \  /  \  /  \
            /    \/    \/    \/    \

███████████████/ /██/ /██/ /██/ /████████████████████████ / / \ / \ / \ / \ ____ / / _/ _/ _/ \ o _, / / ___/ ` |/ ███╗ ███╗ █████╗ ███╗ ███╗██████╗ █████╗ ████╗ ████║██╔══██╗████╗ ████║██╔══██╗██╔══██╗ ██╔████╔██║███████║██╔████╔██║██████╔╝███████║ ██║╚██╔╝██║██╔══██║██║╚██╔╝██║██╔══██╗██╔══██║ ██║ ╚═╝ ██║██║ ██║██║ ╚═╝ ██║██████╔╝██║ ██║ ╚═╝ ╚═╝╚═╝ ╚═╝╚═╝ ╚═╝╚═════╝ ╚═╝ ╚═╝ mamba (0.24.0) supported by @QuantStack GitHub: https://github.com/mamba-org/mamba Twitter: https://twitter.com/QuantStack █████████████████████████████████████████████████████████████ Looking for: [‘xcdat’] conda-forge/osx-arm64 Using cache conda-forge/noarch Using cache Transaction Prefix: ~/mambaforge/envs/xc030spy532mat352 Updating specs:

  • xcdat Package Version Build Channel Size ──────────────────────────────────────────────────────────────────────────────────────────────── Install: ────────────────────────────────────────────────────────────────────────────────────────────────
  • bokeh 2.4.3 pyhd8ed1ab_3 conda-forge/noarch 14MB …
  • cf_xarray 0.7.4 pyhd8ed1ab_0 conda-forge/noarch Cached …
  • dask 2022.8.0 pyhd8ed1ab_1 conda-forge/noarch 5kB
  • dask-core 2022.8.0 pyhd8ed1ab_0 conda-forge/noarch Cached …
  • hdf4 4.2.15 hc683e77_4 conda-forge/osx-arm64 928kB
  • hdf5 1.12.2 nompi_h8968d4b_100 conda-forge/osx-arm64 Cached …
  • libgfortran 5.0.0.dev0 11_0_1_hf114ba7_23 conda-forge/osx-arm64 Cached
  • libgfortran5 11.0.1.dev0 hf114ba7_23 conda-forge/osx-arm64 Cached
  • liblapack 3.9.0 16_osxarm64_openblas conda-forge/osx-arm64 13kB
  • libnetcdf 4.8.1 nompi_h996a5af_104 conda-forge/osx-arm64 1MB …
  • netcdf4 1.6.0 nompi_py310h9d42ac0_101 conda-forge/osx-arm64 Cached
  • numpy 1.23.1 py310h0a343b5_0 conda-forge/osx-arm64 Cached …
  • python 3.10.5 h71ab1a4_0_cpython conda-forge/osx-arm64 Cached …
  • xarray 2022.6.0 pyhd8ed1ab_1 conda-forge/noarch Cached + xcdat 0.2.0 pyhd8ed1ab_0 conda-forge/noarch Cached
  • xorg-libxau 1.0.9 h27ca646_0 conda-forge/osx-arm64 Cached …

What did you expect to happen?

I had expected 0.3.0 to be installed, as per availability through the xcdat conda-forge channel

Minimal Complete Verifiable Example

$ conda create --dry-run -n xc030 -c conda-forge xcdat

  xcdat              conda-forge/noarch::xcdat-0.2.0-pyhd8ed1ab_0

Relevant log output

See above

Anything else we need to know?

Nil

Environment

Nil

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 42

Commits related to this issue

Most upvoted comments

@durack1, referring to https://github.com/xCDAT/xcdat/issues/315#issuecomment-1233440830, I think I misunderstood what the purpose of your YAML file was. I thought it was a meta.yaml that defines a conda recipe. These have selectors like I suggested.

You have a yaml file for the environment. In that case, I think you’re going to either have to have a yaml file per platform or you’re going to have to do the templating yourself using jinja. I don’t think all this run_constrained stuff applies to the type of yaml file you’re creating. That’s also specifically for a conda recipe (meta.yaml) as I understand it.

@tomvothecoder ok great, this solves the regridder.py and dev.yml tweaks, so I should have enough to go on with this. I am a little strapped for time, so will hope to do this sometime late next, early the following week