-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use micromamba 2.0.5.rc0 in Dockerimage #2183
Conversation
This only changes the |
@JohanMabille this is the line you need: |
@mathbunnyru ah indeed, thanks a lot! |
--root-prefix="${CONDA_DIR}" \ | ||
--prefix="${CONDA_DIR}" \ | ||
--yes \ | ||
'jupyter_core' \ | ||
'conda' \ | ||
'mamba' \ | ||
'mamba=2.0.5.rc0' \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the paranoid:
'mamba=2.0.5.rc0' \ | |
'conda-forge/label/mamba_prerelease::mamba=2.0.5.rc0' \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The logs show that mamba 2.0.5.rc0 is installed
@mathbunnyru For a reason I don't understand, it seems that the failing tests are using mamba 1 instead of mamba 2. This looks like a caching issue in the CI. |
Ok let's close this and open a new PR. |
This is just for testing the latest pre-release of micromamba (i.e. 2.0.5.rc0) before releasing for good. I don't know if this is enough, let me know if additional changes are required.