fix(py3-conda-libmamba-solver): Cherrypick upstream commits to add support for libmamba 2.0 #34145
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have already released packages updates to libmamba and subpackages which is a major version jump from 1.5 to 2.0.
This caused failures in the conda packages and images due to py3-conda-libmamba-solver not yet supporting libmamba 2.0.
There is not yet an upstream release of conda-libmamba-solver with mamba 2.0 support but there is a release candidate
branch @ https://github.com/conda/conda-libmamba-solver/tree/24.11.0rc awaiting release.
We have broken dependent packages so we cannot wait for upstream to release.
As such I have cherrypicked the relevant 2.0 support commits from the 24.11.0rc branch.
This resolves the issues seen with conda and libmamba.
Full diff for conda-libmamba-solver @ conda/conda-libmamba-solver@24.9.0...24.11.0rc
mamba-org/mamba#3506 was the most helpful in finding the work to support libmamba 2.0
Signed-off-by: philroche phil.roche@chainguard.dev