You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My problem is not solved in the Troubleshooting docs
Anaconda default channels
I do NOT use the Anaconda default channels (pkgs/* etc.)
How did you install Mamba?
Micromamba
Search tried in issue tracker
update --all
Latest version of Mamba
My problem is not solved with the latest version
Tried in Conda?
I do not have this problem with Conda, just with Mamba
Describe your issue
TLDR: When I activate a mamba (not micromamba!) environment and run micromamba update --all -y --platform osx-arm64, micromamba pretends to update the activated environment but doesn't actually.
Longer story: I have a really weird setup, but maybe it does uncover some unintended behaviour more generally. As part of a general system update procedure I run daily, I activate and update all sorts of conda/mamba/micromamba environments.
Recently, something weird started to happen without having done any changes to the commands invoked: micromamba seemed to perform the same update every time I ran the update command - but it didn't actually change anything. What I'm doing is definitely somewhat weird, but micromamba is still behaving unexpectedly so bear with me.
The interesting thing here seems to be that mamba activate py11 works, but micromamba activate py11 doesn't work, yet the mamba activate affects micromamba commands later on:
❯ micromamba activate py11
critical libmamba Cannot activate, prefix does not exist at: '/Users/corneliusromer/micromamba/envs/py11'
Maybe this makes it reproducible:
Install mamba v2.0.2 and micromamba v2.0.2
Add the wrappers to the shell init:
# >>> conda initialize >>># !! Contents within this block are managed by 'conda init' !!
__conda_setup="$('/opt/homebrew/Caskroom/miniforge/base/bin/conda''shell.zsh''hook'2> /dev/null)"if [ $?-eq 0 ];theneval"$__conda_setup"elseif [ -f"/opt/homebrew/Caskroom/miniforge/base/etc/profile.d/conda.sh" ];then."/opt/homebrew/Caskroom/miniforge/base/etc/profile.d/conda.sh"elseexport PATH="/opt/homebrew/Caskroom/miniforge/base/bin:$PATH"fifiunset __conda_setup
if [ -f"/opt/homebrew/Caskroom/miniforge/base/etc/profile.d/mamba.sh" ];then."/opt/homebrew/Caskroom/miniforge/base/etc/profile.d/mamba.sh"fi# <<< conda initialize <<<# >>> mamba initialize >>># !! Contents within this block are managed by 'micromamba shell init' !!export MAMBA_EXE='/Users/corneliusromer/.local/bin/micromamba';export MAMBA_ROOT_PREFIX='/Users/corneliusromer/micromamba';
__mamba_setup="$("$MAMBA_EXE" shell hook --shell zsh --root-prefix "$MAMBA_ROOT_PREFIX"2> /dev/null)"if [ $?-eq 0 ];theneval"$__mamba_setup"elsealias micromamba="$MAMBA_EXE"# Fallback on help from micromamba activatefiunset __mamba_setup
# <<< mamba initialize <<<
Create an environment py11 with yaml see below
Run mamba activate py11
Run micromamba update --all -y --platform osx-arm64 --log-level 4
Run mamba deactivate
Rinse repeat, observe that the same changes are done every time, suggesting the update isn't actually going through
Troubleshooting docs
Anaconda default channels
How did you install Mamba?
Micromamba
Search tried in issue tracker
update --all
Latest version of Mamba
Tried in Conda?
I do not have this problem with Conda, just with Mamba
Describe your issue
TLDR: When I activate a mamba (not micromamba!) environment and run
micromamba update --all -y --platform osx-arm64
, micromamba pretends to update the activated environment but doesn't actually.Longer story: I have a really weird setup, but maybe it does uncover some unintended behaviour more generally. As part of a general system update procedure I run daily, I activate and update all sorts of conda/mamba/micromamba environments.
Recently, something weird started to happen without having done any changes to the commands invoked: micromamba seemed to perform the same update every time I ran the update command - but it didn't actually change anything. What I'm doing is definitely somewhat weird, but micromamba is still behaving unexpectedly so bear with me.
The interesting thing here seems to be that
mamba activate py11
works, butmicromamba activate py11
doesn't work, yet themamba
activate affectsmicromamba
commands later on:Maybe this makes it reproducible:
py11
with yaml see belowmamba activate py11
micromamba update --all -y --platform osx-arm64 --log-level 4
mamba deactivate
mamba info / micromamba info
Logs
environment.yml
~/.condarc
The text was updated successfully, but these errors were encountered: