Huh, so I fixed it. This is what I did:
First--with defaults as the only channel, tried conda update -n base conda and conda update -n base conda -c defaults again, neither worked.
Then saw your post, and ran conda config --show-sources:
==> /home/mainacct/anaconda2/.condarc <==
pinned_packages:
- bioconda::weblogo
- schrodinger::pymol-psico
- schrodinger::pymol
- anaconda::anaconda
- anaconda::conda
==> /home/mainacct/.condarc <==
ssl_verify: True
channels:
- defaults
channel_priority: False
This reminded me I had conda pinned to the anaconda channel (whoops) and this appears to have worked:
conda update -n base conda -c anaconda:
Solving environment: done
## Package Plan ##
environment location: /home/mainacct/anaconda2
added / updated specs:
- conda
The following packages will be downloaded:
package | build
---------------------------|-----------------
certifi-2017.11.5 | py27h71e7faf_0 196 KB anaconda
conda-4.4.4 | py27_0 621 KB anaconda
openssl-1.0.2n | hb7f436b_0 3.4 MB anaconda
------------------------------------------------------------
Total: 4.2 MB
The following packages will be UPDATED:
certifi: 2017.11.5-py27h71e7faf_0 --> 2017.11.5-py27h71e7faf_0 anaconda
conda: 4.4.3-py27_0 anaconda --> 4.4.4-py27_0 anaconda
openssl: 1.0.2n-hb7f436b_0 --> 1.0.2n-hb7f436b_0 anaconda
Proceed ([y]/n)? y
Downloading and Extracting Packages
certifi 2017.11.5: ############################################################################################################ | 100%
conda 4.4.4: ################################################################################################################## | 100%
openssl 1.0.2n: ############################################################################################################### | 100%
Preparing transaction: done
Verifying transaction: done
Executing transaction: done
After that, conda info to check installation:
active environment : None
user config file : /home/mainacct/.condarc
populated config files : /home/mainacct/anaconda2/.condarc
/home/mainacct/.condarc
conda version : 4.4.4
conda-build version : 3.2.0
python version : 2.7.14.final.0
base environment : /home/mainacct/anaconda2 (writable)
channel URLs : https://repo.continuum.io/pkgs/main/linux-64
https://repo.continuum.io/pkgs/main/noarch
https://repo.continuum.io/pkgs/free/linux-64
https://repo.continuum.io/pkgs/free/noarch
https://repo.continuum.io/pkgs/r/linux-64
https://repo.continuum.io/pkgs/r/noarch
https://repo.continuum.io/pkgs/pro/linux-64
https://repo.continuum.io/pkgs/pro/noarch
package cache : /home/mainacct/anaconda2/pkgs
/home/mainacct/.conda/pkgs
envs directories : /home/mainacct/anaconda2/envs
/home/mainacct/.conda/envs
platform : linux-64
user-agent : conda/4.4.4 requests/2.18.4 CPython/2.7.14 Linux/4.10.0-42-generic ubuntu/16.04 glibc/2.23
UID:GID : 1000:1000
netrc file : None
offline mode : False
This might be irrelevant to you at this point, but for the hell of it I ran conda update -n base conda (i.e. without specifying anaconda channel) and got this:
Solving environment: done
## Package Plan ##
environment location: /home/mainacct/anaconda2
added / updated specs:
- conda
The following packages will be downloaded:
package | build
---------------------------|-----------------
certifi-2017.11.5 | py27h71e7faf_0 196 KB
openssl-1.0.2n | hb7f436b_0 3.4 MB
------------------------------------------------------------
Total: 3.6 MB
The following packages will be UPDATED:
certifi: 2017.11.5-py27h71e7faf_0 anaconda --> 2017.11.5-py27h71e7faf_0
openssl: 1.0.2n-hb7f436b_0 anaconda --> 1.0.2n-hb7f436b_0
Proceed ([y]/n)? y
Downloading and Extracting Packages
certifi 2017.11.5: ############################################################################################################ | 100%
openssl 1.0.2n: ############################################################################################################### | 100%
Preparing transaction: done
Verifying transaction: done
Executing transaction: done
I'm guessing the anaconda::conda pin was the problem, huh?
If you have time, now I have a few questions (can also ask them somewhere else since this is off-topic from the issues):
Is there are reason to not have the pins anaconda::conda and anaconda::anaconda, aside from me forgetting they existed? I did so because before I pinned them I tended to get mixed installations of conda (even before conda-forge was at a higher priority than defaults) and the package lists at anaconda.org seemed to indicate the anaconda channel had the highest version of conda for 2.7.
Would it be safer to install conda/anaconda from defaults?
How does the defaults channel work, and how is it different from the anaconda channel in terms of how it gets packages, which ones go into it, and the stability of said packages?
I read the best practices is to install packages to a new environment rather than the base. I guess I assumed that most packages outside "special" channels (like bioconda/schrodinger/r) would be needed across all environments. Am I confused?
Thanks for your help!
#######################
Illegal instruction (core dumped) 问题解决办法
conda install -c conda-forge tensorflow
