jaimergp

> You could detach environments from their folder with `pixi`: https://pixi.sh/latest/reference/pixi_configuration/#detached-environments. That's only for `.pixi/envs` right? The current workflow assumes a single environment for `conda-build`, which gets installed to e.g....

We don't use Go for anything. Push an empty commit to see if it was a flaky thing on Netlify's side and if not I'll check tomorrow.

> Are you planning on part 2/∞? Yes! This is just the beginning, and not ready for publication yet. Was hoping to gather some interest here and get comments from...

I added: - https://github.com/conda-forge/staged-recipes/pull/27765 - https://github.com/conda-forge/conda-smithy/pull/2077 With those merged and released we can close this.

Thank you so much @msarahan, that adds so much context!

It looks like something went wrong in the base environment when installing something else. The good news is that this is coming from the code that handles the CUDA detection...

Is this a permissions issue? Notice this line: ``` C:\dev\software\miniconda3 (read only) ``` Can you try installing it in a different location where you have permissions? Or give `C:\dev\software\miniconda3` write...

I think that build of libxml2 2.14 was marked as broken so the faulty upgrade should not happen again.

Ah no, this is still needed: https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/998

Transferred over to `conda/conda-libmamba-solver` so we take another look. Thanks!