2.9.0 not picked up in openPMD-api about adios2-feedstock HOT 6 CLOSED

btw, do we need to declare pinning of versions in the package itself?

Yes, we have that. Any package that links adios2 (or libadios2) will have a runtime dependency pinned to the patch version and mpi variant.

It was the hdf5 1.14.1 migration - adios2 had been updated to 1.14.1, while openpmd-api was still on 1.12, so it picked the latest adios2 package that accepted a compatible hdf5. I'm not sure why the bot never issued a PR to openpmd-api, but claimed that openpmd-api had been migrated, when it hadn't. conda-forge/openpmd-api-feedstock#107 should fix it.

from adios2-feedstock.

very likely to be a pinned dependency somewhere, I'll see if I can figure it out

from adios2-feedstock.

For detail, the Python 3.10 mpich build of openpmd-api in conda-forge/openpmd-api-feedstock#107 (osx_arm64_mpimpichnumpy1.21python3.10.____cpython) gets this for runtime dependencies:

  run:
    - python_abi 3.10.* *_cp310
    - adios * mpi_mpich_*
    - numpy >=1.21.6,<2.0a0
    - libcxx >=15.0.7
    - blosc >=1.21.4,<2.0a0
    - libzlib >=1.2.13,<1.3.0a0
    - mpich >=4.1.2,<5.0a0
    - adios2 >=2.9.1,<2.9.2.0a0 mpi_mpich_*
    - python >=3.10,<3.11.0a0
    - hdf5 >=1.14.1,<1.14.2.0a0 mpi_mpich_*
    - bzip2 >=1.0.8,<2.0a0
    - mpi4py
    - zlib

I suspect adios should have a version pin in its run_exports as well, instead of *? Or does it not have ABI compatibility issues?

from adios2-feedstock.

@minrk thank you, let me know what you find :)

from adios2-feedstock.

btw, do we need to declare pinning of versions in the package itself?

re: #76 (comment)

from adios2-feedstock.

Oh, yes let's add this to adios!
I opened a PR in conda-forge/adios-feedstock#36

from adios2-feedstock.