conda_build_tool: mambabuild broken by latest conda-smithy

[traversaro]

Comment:

Opening this as a question instead of a bug, as I am not sure if this is intentional or not.

With #1844 (that was released in 3.31.0), feedstocks that have conda_build_tool: mambabuild can't build, as the CI tries to install both boa and conda-build>=24.1, that as of today fails with:

traversaro@IITBMP014LW012:~$ mamba create -n testgazclas boa 'conda-build>=24.1'

Looking for: ['boa', "conda-build[version='>=24.1']"]

conda-forge/linux-64                                        Using cache
conda-forge/noarch                                          Using cache
Could not solve for environment specs
The following packages are incompatible
├─ boa is installable with the potential options
│  ├─ boa [0.1.0|0.1.2|...|0.3.0] would require
│  │  └─ conda-build 3.20.* , which can be installed;
│  ├─ boa [0.10.0|0.11.0|...|0.9.0] would require
│  │  └─ conda-build >=3.20,<3.22 , which can be installed;
│  ├─ boa [0.11.0|0.12.0|0.13.0] would require
│  │  └─ conda-build >=3.20,<3.23 , which can be installed;
│  ├─ boa [0.13.0|0.14.0] would require
│  │  └─ conda-build >=3.20,<3.24 , which can be installed;
│  ├─ boa 0.14.0 would require
│  │  └─ conda-build >=3.24,<3.25 , which can be installed;
│  ├─ boa 0.15.1 would require
│  │  └─ conda-build >=3.24,<3.26 , which can be installed;
│  └─ boa 0.16.0 would require
│     └─ conda-build >=3.24,<24.1.0a0 , which can be installed;
└─ conda-build >=24.1  is not installable because it conflicts with any installable versions previously reported.

See conda-forge/gazebo-feedstock#203 .