micromamba: mamba
and micromamba
behave differently, despite being the same executable
#201341
Open
4 tasks done
Labels
bug
Reproducible Homebrew/homebrew-core bug
brew gist-logs <formula>
link ORbrew config
ANDbrew doctor
outputVerification
brew doctor
output saysYour system is ready to brew.
and am still able to reproduce my issue.brew update
and am still able to reproduce my issue.brew doctor
and that did not fix my problem.What were you trying to do (and why)?
Related, I think, to #200954, but not the same.
The install caveat for the
micromamba
formula encourages you to invoke micromamba asmamba
(emphasis added):And
micromamba
is a symlink tomamba
:Plus there is this comment in #200954 :
So on this basis I expect that I should be able to run
micromamba activate somenv
andmamba activate somenv
and that these two commands would do exactly the same thing.What happened (include all command output)?
OK, that works great. But if I do the same thing calling
mamba
, in a fresh shell:Except here's the relevant section of my config.fish:
Even if I re-run the exact
mamba shell init
command recommended in the mamba error message (setting up~/.local/share/mamba
as my prefix rather than~/Library/Application Support/micromamba
), runningmamba activate
in a fresh shell just produces the same error. The only way to use micromamba is to invoke it asmicromamba
.What did you expect to happen?
mamba
andmicromamba
should be synonyms; alternatively,mamba
should provide an error message that actually explains how to fix whatever it objects to, rather than telling me to do something I've already done.Step-by-step reproduction instructions (by running
brew
commands)The text was updated successfully, but these errors were encountered: