I have a similar problem as @joanmanel and have no CONDA_* variables in env... but it is not "/opt/miniconda3/pkgs/" but "/opt/miniconda3/lib/python3.11/site-packages/" where the conflicts lie.
I also manually activate conda, so there is no need to uncomment any lines, and conda is deactivated.
Pinned Comments
user7z commented on 2024-09-19 23:08 (UTC)
it gives this error :
Error while loading conda entry point: conda-content-trust (OpenSSL 3.0's legacy provider failed to load. This is a fatal error by default, but cryptography supports running without legacy algorithms by setting the environment variable CRYPTOGRAPHY_OPENSSL_NO_LEGACY. If you did not expect this error, you have likely made a mistake with your OpenSSL configuration.)
the solution is to put this : " export CRYPTOGRAPHY_OPENSSL_NO_LEGACY='1' " into /etc/profile.d/conda.sh
carlosal1015 commented on 2024-07-10 02:47 (UTC)
In order to check a new version
carlosal1015 commented on 2022-05-26 20:15 (UTC) (edited on 2022-05-26 20:15 (UTC) by carlosal1015)
Important note: This is the way how to upgrade.
Suppose that we have this line in
~/.bashrc
or~/.zshrc
or etc.jadelord commented on 2021-02-05 09:50 (UTC) (edited on 2022-02-03 11:32 (UTC) by jadelord)
I have packaged micromamba in AUR. Try it if you are looking for a lightweight, barebones alternative to miniconda.