mamba reports archspec as x86_64-v3, but this feedstock expects it as x86_64_v3

[traversaro]

Comment:

I am not sure which one is correct, but I noticed an inconsistencies between mamba and this repo. This repo supports x86_64_v3 as possible microarchitecture, but the __archspec value reported by mamba is instead x86_64-v3 (the difference is last underscore that is a dash), see:

• https://github.com/mamba-org/mamba/blob/83fdeae46572a05a1657395cccccbab74e8710d3/libmamba/src/core/virtual_packages.cpp#L177-L191

• microarch-level-feedstock/recipe/conda_build_config.yaml

  Line 15 in 1b446db

  - x86_64_v3

As a consequence of this, the packages in this feedstock can't be installed via mamba/micromamba.

Related issue on the mamba side: mamba-org/mamba#3222 .

fyi @conda-forge/microarch-level

[matthewfeickert]

@conda-forge/microarch-level I'm seeing this over on conda-forge/boost-histogram-feedstock#57 (comment) as well.

As a consequence of this, the packages in this feedstock can't be installed via mamba/micromamba.

This is pretty serious, as this means that all packages built with microarch level support will be uninstallable with mamba/micromamba, which means they're effectively broken.

[traversaro]

The issue was fixed in mamba-org/mamba#3404, I guess we actually need a release of mamba to actually fix it (or backport the patch to the mamba feedstock). fyi @conda-forge/micromamba @conda-forge/mamba

[matthewfeickert]

Things are fixed now: mamba-org/mamba#3404 (comment)

[traversaro]

Yes, as of mamba 1.5.10 . The default miniforge3 installed probably still installs an older mamba in the base environment, so to use archspec-enabled packages make sure to run conda update -n base mamba.