jaimergp

Ok, it comes from here https://github.com/conda/conda-build/blob/cf35214183b6e549675874ed37c7e01c6b7322dc/conda_build/metadata.py#L2224-L2227 Because of the Jinja `{% if ...}` eliding some outputs, this causes some mismatch in how outputs are parsed and text-retrieved. The resulting tuples...

conda-build could export a new subcommand plugin for this, setting the right context variables. I don't know if this might result into conflicts with boa's mambabuild subcommand (who wins a...

This would be all the Python code you need: In let's say `conda_mambabuild.py`: ```python from conda import plugins from conda.common.io import env_var def mambabuild(*args): from conda_build.cli.main_build import execute with env_var("CONDA_SOLVER",...

You can export `CONDA_USE_ONLY_TAR_BZ2=True` for this :)

I think this was fixed in 23.9.0 via https://github.com/conda/conda-libmamba-solver/pull/274. Your `conda info` reports 23.7.0, so I'd try upgrading first to see if the issue you brought up is already addressed...

not stale

not stale

From 23.9.0 on, conda-libmamba-solver won't try to use channels that are unavailable. I'd recommend to upgrade. To prevent the error, you can set [this environment variable](https://conda.github.io/conda-libmamba-solver/user-guide/configuration/#advanced-options): `CONDA_LIBMAMBA_SOLVER_NO_CHANNELS_FROM_INSTALLED=1`.

Sorry, that's a typo. You need conda-libmamba-solver 24.11 or later.

That key is an environment variable btw, not a setting. It should work with 24.9 and earlier.