You don't need to keep the conda-exec around. Try a new shell and see if conda is working. The -force-reinstall flag might be useful if it claims the requirement is already satisfed. Make sure that the build of Conda that is suggested corresponds to the version of Python currently installed. (Re-)Install the conda package in the base env.
Option 2: Install conda for the Current Python Start a new shell and try using conda again. Identify the revision immediately before the current one (we'll denote it by here), and attempt to restore it. You should also see the pkgs folder in your base env in the package cache. The key thing to check for is that base environment: correctly identifies to where your base env is and shows it as (writable).
Typically this is the anaconda3 or miniconda3 folder in this case, we'll use the path given by OP: export CONDA_ROOT_PREFIX=/home/me/anaconda2 Temporarily set CONDA_ROOT_PREFIX to the base of your install. Tar -xzOf conda-standalone-4.9.2.tar.bz2 standalone_conda/conda.exe > conda-exec I'm going to rename it to conda-exec anyway: # download archive
exe it's a binary and should run when called at the shell. The actual binary will be at conda_standalone/conda.exe in the. Please report in the comments if this works or needs adjusting!ĭownload the appropriate standalone Conda for your platform (here we'll use linux-64/conda-standalone-4.9.2). You can do all the following from any directory, so maybe use a temp or wherever you put downloads. One possible route to recovery is to temporarily use a standalone build of the conda-exec to repair your base env. This sounds like something the dependency resolver is overlooking - i.e., default behavior should be to protect integrity of base environment where conda lives.
It is problematic that many packages on Anaconda seem to be triggering Python version changes, but not subsequently triggering a conda package update. The Python package is necessary for Conda as a whole to function and it get's loaded whenever you try to use conda. The Python version change (2.7.14 -> 3.6.8) created a situation where the new python has a new site-packages which no longer contains a conda package, whereas if you only update within 2.7.x, this wouldn't be an issue.Ĭonda includes both a set of binaries (e.g., what you're invoking when you type conda in a shell) and a Python package by the same name. Changing Python versions without updating the conda package breaks Conda.