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
mamba remove package doesn't respect --force flag #412
Comments
My workaround at the moment is to install conda in the environment, and to use that for the mamba activate $MY_ENV
mamba install conda -c defaults --yes
conda remove --force $OFFENDING_PACKAGE But ideally mamba will be able to do that soon :) |
I have been giving this some thought and it will require us to re-engineer slightly our current "Transaction" class to be able to handle "explicit" transactions as well. Explicit transactions will not go through the solver, but rather either use URLs / files or the forced removal of an installed spec. Having this would also be nice so that we can consolidate our current micromamba explicit environmetn file handling. |
+1 for this |
Co-authored-by: AJ Schmidt <ajschmidt8@users.noreply.github.com>
Closing this as recent discussion is in #1523 |
So the plan is to always have the mamba api differ from conda here? If so I think we need to have mamba error if people try the command. |
I just meant to say we should continue discussing in the other ticket. |
If I “close as duplicate” in GitHub it days “closed as not planned” which doesn’t make sense |
Ahhhhh got it. Great and thank you! |
Or has different (IMHO undesirable) behaviour from
conda
.With
conda
the--force
flag allows you to remove a package without uninstalling every package which depends on it - e.g.Whilst it will leave your environment in an inconsistent state, IMHO if you use
--force
it's up to you to deal with the consequences. This can be very useful in cases where you e.g. want to use a develop/editable install.In any case, trying the same with
mamba
basically wants to uninstall the entire environment:The text was updated successfully, but these errors were encountered: