jaimergp

Even if we have two installers generated, so far the info.json contents would have been the same (both installers bundle the same packages), but if we are going to add...

@marcoesters is this still relevant or did we forget to close?

I forgot to add something about the (concerning?) overlaps with `conda list`. This is probably worth its own issue but right now we have: - `conda list`: enumerates packages in...

Any updates here @jezdez?

Woohoo!

> Yep, when this PR was started we only barely started the discussion that may end in something like https://github.com/conda/conda/pull/14870, I've asked for review for a bit now. Ok, I...

That comes directly from `libmamba`: https://github.com/conda/conda-libmamba-solver/blob/3eee64ade3921e28f407372074db3e8e4fbc49e5/conda_libmamba_solver/solver.py#L399-L403 With the `-vvv` logs we'll be able to see which job the offending spec was part of and then propose workarounds but yea, this...

Thanks for the gist @stevenbedrick! I see this block here: ``` DEBUG conda.conda_libmamba_solver.solver:_solve_attempt(391): Adding task USERINSTALLED info libmamba Parsing MatchSpec conda-forge/linux-64::python==3.12.2=hab00c5b_0_cpython info libmamba Adding job: conda-forge/linux-64::python==3.12.2=hab00c5b_0_cpython info libmamba Parsing MatchSpec...

That looks alright 🤔 If you are comfortable patching your local installation a bit, this is what I would try. Open `${base_environment}/lib/python3.*/site-packages/conda_libmamba_solver/solver.py` and find this block to edit (under `Solver._solve_attempt()`):...