Miniconda installation

Users
1

Dear community

I tried to install miniconda based on the link here:
Installing Miniconda — Anaconda documentation

However, I got the following error (fig 1), so it seems that miniconda is not installed at all, although it seems that miniconda is there (fig 2).

Indeed on the path directory there is no miniconda, but I am struggling around with the advice here. What do I need to replace and at the place?

Replace <FILE_NAME> with the path to your installer

Get-FileHash <FILE_NAME> -Algorithm SHA256

Kind regards
Sibylle

fig1
fig1861×337 38.7 KB

fig2
fig2854×656 108 KB

2

you need to use one of the Conda promts for your command Window: I think the one called “Anaconda Powershell Prompt (miniconda3)” – if you want powershell.

Those are set up with conda configured to be on your PATH, and all that.

3

Dear Chris

I used to Anaconda Powershell Prompt (minionda3)

image
image1579×930 36.2 KB

env-invest seems to be activated, but there are still some erorrs. It still seems to be tha “name & path”:

. : The name ‘C:\Users\Sibylle St÷ckli.conda\envs\env-invest\etc\conda\activate.d\openssl_activate.ps1’ was not recognised as the name of a cmdlet, a function
was not recognised as the name of a cmdlet, a function, a script file or an executable program. Please check
the spelling of the name, or whether the path is correct (if included), and repeat the process.
In line:12 Characters:3

Kind regards
Sibylle

4

It looks like there again may be an issue with the path containing your username, specifically the space and/or the diacritics. I see that the ö shows up incorrectly as a division symbol under “active environment”. Possibly there is some encoding mismatch between conda and the terminal.

In the past when I had such problems, I created a “link” that provided an alternative name to the user directory. Windows has two kinds called symbolic links and “directory junctions”; in the past I used junctions but I’m not up on whether that’s still the best choice under Windows 10/11. Here is one link with some information.

In any case, you might try creating such a junction with a “safe” name like “FakeSybille” and then working from within that instead of the actual user directory. If done right I think the junction can act as an “alias” so that you or whatever apps you’re using don’t need to actually see the problematic username in the path.

5

Dear Dasha and Bren
I changed now to my institutional computer as I got a dedicated (Personal) virtual machine. In this way I am able to install miniconda with a suitable user name.
However I got no the following errors:

(base) C:\Users\f80809100>conda create -n env-invest “python=3.11”
Channels:

  • defaults
    Platform: win-64
    Collecting package metadata (repodata.json): - Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/win-64/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/noarch/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/noarch/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/win-64/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/win-64/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/noarch/repodata.json.zst

  • Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/noarch/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/noarch/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/win-64/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/win-64/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/win-64/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/noarch/repodata.json.zst

  • Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/noarch/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/noarch/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/win-64/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/win-64/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/win-64/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/noarch/repodata.json.zst

failed

CondaSSLError: Encountered an SSL error. Most likely a certificate verification issue.

Exception: HTTPSConnectionPool(host=‘repo.anaconda.com’, port=443): Max retries exceeded with url: /pkgs/main/win-64/repodata.json.zst (Caused by SSLError(SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)))

(base) C:\Users\f80809100>conda activate env-invest

EnvironmentNameNotFound: Could not find conda environment: env-invest
You can list all discoverable environments with conda info --envs.

(base) C:\Users\f80809100>conda install natcap.invest -c conda-forge
Channels:

  • conda-forge
  • defaults
    Platform: win-64
    Collecting package metadata (repodata.json): \ Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/noarch/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/win-64/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/noarch/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/noarch/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/win-64/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/win-64/repodata.json.zst

/ Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /conda-forge/win-64/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /conda-forge/noarch/repodata.json.zst

\ Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/noarch/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/win-64/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/win-64/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/win-64/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/noarch/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/noarch/repodata.json.zst

/ Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /conda-forge/noarch/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /conda-forge/win-64/repodata.json.zst

  • Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/noarch/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/win-64/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/noarch/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/noarch/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/win-64/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/win-64/repodata.json.zst

/ Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /conda-forge/win-64/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /conda-forge/noarch/repodata.json.zst

failed

CondaSSLError: Encountered an SSL error. Most likely a certificate verification issue.

Exception: HTTPSConnectionPool(host=‘conda.anaconda.org’, port=443): Max retries exceeded with url: /conda-forge/win-64/repodata.json.zst (Caused by SSLError(SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)))

Mindiconda is installed:

packages in environment at C:\Users\f80809100\AppData\Local\miniconda3:

Name Version Build Channel

anaconda-anon-usage 0.4.4 py312hfc23b7f_100
archspec 0.2.3 pyhd3eb1b0_0
boltons 23.0.0 py312haa95532_0
brotli-python 1.0.9 py312hd77b12b_8
bzip2 1.0.8 h2bbff1b_6
ca-certificates 2024.3.11 haa95532_0
certifi 2024.6.2 py312haa95532_0
cffi 1.16.0 py312h2bbff1b_1
charset-normalizer 2.0.4 pyhd3eb1b0_0
colorama 0.4.6 py312haa95532_0
conda 24.5.0 py312haa95532_0
conda-content-trust 0.2.0 py312haa95532_1
conda-libmamba-solver 24.1.0 pyhd3eb1b0_0
conda-package-handling 2.3.0 py312haa95532_0
conda-package-streaming 0.10.0 py312haa95532_0
console_shortcut_miniconda 0.1.1 haa95532_2
cryptography 42.0.5 py312h89fc84f_1
distro 1.9.0 py312haa95532_0
expat 2.6.2 hd77b12b_0
fmt 9.1.0 h6d14046_1
frozendict 2.4.2 py312haa95532_0
idna 3.7 py312haa95532_0
jsonpatch 1.33 py312haa95532_1
jsonpointer 2.1 pyhd3eb1b0_0
libarchive 3.6.2 hb62f4d4_3
libcurl 8.7.1 h86230a5_0
libffi 3.4.4 hd77b12b_1
libiconv 1.16 h2bbff1b_3
libmamba 1.5.8 h99b1521_2
libmambapy 1.5.8 py312h77c03ed_2
libsolv 0.7.24 h23ce68f_1
libssh2 1.11.0 h291bd65_0
libxml2 2.10.4 h0ad7f3c_2
lz4-c 1.9.4 h2bbff1b_1
menuinst 2.1.1 py312h5da7b33_0
openssl 3.0.14 h827c3e9_0
packaging 23.2 py312haa95532_0
pcre2 10.42 h0ff8eda_1
pip 24.0 py312haa95532_0
platformdirs 3.10.0 py312haa95532_0
pluggy 1.0.0 py312haa95532_1
powershell_shortcut_miniconda 0.0.1 haa95532_2
pybind11-abi 5 hd3eb1b0_0
pycosat 0.6.6 py312h2bbff1b_1
pycparser 2.21 pyhd3eb1b0_0
pysocks 1.7.1 py312haa95532_0
python 3.12.4 h14ffc60_1
reproc 14.2.4 hd77b12b_2
reproc-cpp 14.2.4 hd77b12b_2
requests 2.32.2 py312haa95532_0
ruamel.yaml 0.17.21 py312h2bbff1b_0
setuptools 69.5.1 py312haa95532_0
sqlite 3.45.3 h2bbff1b_0
tk 8.6.14 h0416ee5_0
tqdm 4.66.4 py312hfc267ef_0
truststore 0.8.0 py312haa95532_0
tzdata 2024a h04d1e81_0
urllib3 2.2.2 py312haa95532_0
vc 14.2 h2eaa2aa_1
vs2015_runtime 14.29.30133 h43f2093_3
wheel 0.43.0 py312haa95532_0
win_inet_pton 1.1.0 py312haa95532_0
xz 5.4.6 h8cc25b3_1
yaml-cpp 0.8.0 hd77b12b_1
zlib 1.2.13 h8cc25b3_1
zstandard 0.22.0 py312h3469f8a_0
zstd 1.5.5 hd43e919_2

6

I also tried to install miniconda via “all users”
same error

(base) PS C:\Users\f80809100> conda create -n env-invest “python=3.11”

conda activate env-invest
conda install natcap.invest -c conda-forge
Channels:

  • defaults
    Platform: win-64
    Collecting package metadata (repodata.json): / Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/win-64/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/win-64/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/win-64/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/noarch/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/noarch/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/noarch/repodata.json.zst

| Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/win-64/repodata.json.zst

/ Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/win-64/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/noarch/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/noarch/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/noarch/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/win-64/repodata.json.zst

| Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/noarch/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/win-64/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/win-64/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/noarch/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/noarch/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/win-64/repodata.json.zst

failed

CondaSSLError: Encountered an SSL error. Most likely a certificate verification issue.

Exception: HTTPSConnectionPool(host=‘repo.anaconda.com’, port=443): Max retries exceeded with url: /pkgs/main/win-64/repodata.json.zst (Caused by SSLError(SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)))

EnvironmentNameNotFound: Could not find conda environment: env-invest
You can list all discoverable environments with conda info --envs.

Invoke-Expression : Das Argument kann nicht an den Parameter “Command” gebunden werden, da es sich um eine leere Zeichenfolge handelt.
In C:\ProgramData\miniconda3\shell\condabin\Conda.psm1:76 Zeichen:36

  •     Invoke-Expression -Command $activateCommand;

  •                                ~~~~~~~~~~~~~~~~
    • CategoryInfo : InvalidData: (:slight_smile: [Invoke-Expression], ParameterBindingValidationException
    • FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyStringNotAllowed,Microsoft.PowerShell.Commands.InvokeExpressionCommand

Channels:

  • conda-forge
  • defaults
    Platform: win-64
    Collecting package metadata (repodata.json): \ Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/win-64/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/win-64/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/noarch/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/noarch/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/win-64/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/noarch/repodata.json.zst

/ Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /conda-forge/win-64/repodata.json.zst

Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /conda-forge/noarch/repodata.json.zst

\ Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/win-64/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/win-64/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/noarch/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/noarch/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/win-64/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/noarch/repodata.json.zst

/ Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /conda-forge/noarch/repodata.json.zst

Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /conda-forge/win-64/repodata.json.zst

  • Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/noarch/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/r/win-64/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/win-64/repodata.json.zst

\ Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/noarch/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/main/win-64/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /pkgs/msys2/noarch/repodata.json.zst

/ Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /conda-forge/noarch/repodata.json.zst

Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)’: /conda-forge/win-64/repodata.json.zst

failed

CondaSSLError: Encountered an SSL error. Most likely a certificate verification issue.

Exception: HTTPSConnectionPool(host=‘conda.anaconda.org’, port=443): Max retries exceeded with url: /conda-forge/win-64/repodata.json.zst (Caused by SSLError(SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)’)))

(base) PS C:\Users\f80809100>

7

I also tried now on my old mac, because I think we will not be able to solve the problem on the windows or on the virtual machine.

As far as I see everything is no installed. Howerer there is still a bug I cannot find. Which powershell I need to use on mac, I used “Terminal”.

conda install -p path/to/myenv python=3.11
(base) sibylles-mbp:~ sibyllestockli$ invest list
-bash: invest: command not found
(base) sibylles-mbp:~ sibyllestockli$ invest run --help
-bash: invest: command not found
(base) sibylles-mbp:~ sibyllestockli$

Here the installation:

(base) sibylles-mbp:~ sibyllestockli$ conda install natdcap.invest -c conda-forge
Channels:

  • conda-forge
  • defaults
    Platform: osx-64
    Collecting package metadata (repodata.json): done
    Solving environment: failed

PackagesNotFoundError: The following packages are not available from current channels:

  • natdcap.invest

Current channels:

To search for alternate channels that may provide the conda package you’re
looking for, navigate to

https://anaconda.org

and use the search bar at the top of the page.

(base) sibylles-mbp:~ sibyllestockli$ invest list
-bash: invest: command not found
(base) sibylles-mbp:~ sibyllestockli$ invest run --help
-bash: invest: command not found
(base) sibylles-mbp:~ sibyllestockli$ conda create -n env-invest “python=3.11”

InvalidMatchSpec: Invalid spec ‘“python=3.11”’: Invalid version ‘3.11”’: invalid character(s)

(base) sibylles-mbp:~ sibyllestockli$ conda activate env-invest

EnvironmentNameNotFound: Could not find conda environment: env-invest
You can list all discoverable environments with conda info --envs.

(base) sibylles-mbp:~ sibyllestockli$ conda install natcap.invest -c conda-forgeinvest run --help
usage: conda install [-h] [–revision REVISION] [-n ENVIRONMENT | -p PATH]
[-c CHANNEL] [–use-local] [–override-channels]
[–repodata-fn REPODATA_FNS] [–experimental {jlap,lock}]
[–no-lock] [–repodata-use-zst | --no-repodata-use-zst]
[–strict-channel-priority] [–no-channel-priority]
[–no-deps | --only-deps] [–no-pin] [–copy]
[–no-shortcuts] [–shortcuts-only SHORTCUTS_ONLY] [-C]
[-k] [–offline] [–json] [-v] [-q] [-d] [-y]
[–download-only] [–show-channel-urls] [–file FILE]
[–solver {classic,libmamba}] [–force-reinstall]
[–freeze-installed | --update-deps | -S | --update-all | --update-specs]
[-m] [–clobber] [–dev]
[package_spec …]

Install a list of packages into a specified conda environment.

This command accepts a list of package specifications (e.g, bitarray=0.8)
and installs a set of packages consistent with those specifications and
compatible with the underlying environment. If full compatibility cannot
be assured, an error is reported and the environment is not changed.

Conda attempts to install the newest versions of the requested packages. To
accomplish this, it may update some packages that are already installed, or
install additional packages. To prevent existing packages from updating,
use the --freeze-installed option. This may force conda to install older
versions of the requested packages, and it does not prevent additional
dependency packages from being installed.

If you wish to skip dependency checking altogether, use the ‘–no-deps’
option. This may result in an environment with incompatible packages, so
this option must be used with great caution.

conda can also be called with a list of explicit conda package filenames
(e.g. ./lxml-3.2.0-py27_0.tar.bz2). Using conda in this mode implies the
–no-deps option, and should likewise be used with great caution. Explicit
filenames and package specifications cannot be mixed in a single command.

positional arguments:
package_spec List of packages to install or update in the conda
environment.

options:
-h, --help Show this help message and exit.
–revision REVISION Revert to the specified REVISION.
–file FILE Read package versions from the given file. Repeated
file specifications can be passed (e.g. --file=file1
–file=file2).
–dev Use sys.executable -m conda in wrapper scripts
instead of CONDA_EXE. This is mainly for use during
tests where we test new conda sources against old
Python versions.

Target Environment Specification:
-n ENVIRONMENT, --name ENVIRONMENT
Name of environment.
-p PATH, --prefix PATH
Full path to environment location (i.e. prefix).

Channel Customization:
-c CHANNEL, --channel CHANNEL
Additional channel to search for packages. These are
URLs searched in the order they are given (including
local directories using the ‘file://’ syntax or simply
a path like ‘/home/conda/mychan’ or ‘…/mychan’).
Then, the defaults or channels from .condarc are
searched (unless --override-channels is given). You
can use ‘defaults’ to get the default packages for
conda. You can also use any name and the .condarc
channel_alias value will be prepended. The default
channel_alias is https://conda.anaconda.org/.
–use-local Use locally built packages. Identical to ‘-c local’.
–override-channels Do not search default or .condarc channels. Requires
–channel.
–repodata-fn REPODATA_FNS
Specify file name of repodata on the remote server
where your channels are configured or within local
backups. Conda will try whatever you specify, but will
ultimately fall back to repodata.json if your specs
are not satisfiable with what you specify here. This
is used to employ repodata that is smaller and reduced
in time scope. You may pass this flag more than once.
Leftmost entries are tried first, and the fallback to
repodata.json is added for you automatically. For more
information, see conda config --describe repodata_fns.
–experimental {jlap,lock}
jlap: Download incremental package index data from
repodata.jlap; implies ‘lock’. lock: use locking when
reading, updating index (repodata.json) cache. Now
enabled.
–no-lock Disable locking when reading, updating index
(repodata.json) cache.
–repodata-use-zst, --no-repodata-use-zst
Check for/do not check for repodata.json.zst. Enabled
by default.

Solver Mode Modifiers:
–strict-channel-priority
Packages in lower priority channels are not considered
if a package with the same name appears in a higher
priority channel.
–no-channel-priority
Package version takes precedence over channel
priority. Overrides the value given by conda config --show channel_priority.
–no-deps Do not install, update, remove, or change
dependencies. This WILL lead to broken environments
and inconsistent behavior. Use at your own risk.
–only-deps Only install dependencies.
–no-pin Ignore pinned file.
–solver {classic,libmamba}
Choose which solver backend to use.
–force-reinstall Ensure that any user-requested package for the current
operation is uninstalled and reinstalled, even if that
package already exists in the environment.
–freeze-installed, --no-update-deps
Do not update or change already-installed
dependencies.
–update-deps Update dependencies that have available updates.
-S, --satisfied-skip-solve
Exit early and do not run the solver if the requested
specs are satisfied. Also skips aggressive updates as
configured by the ‘aggressive_update_packages’ config
setting. Use ‘conda info --describe
aggressive_update_packages’ to view your setting.
–satisfied-skip-solve is similar to the default
behavior of ‘pip install’.
–update-all, --all Update all installed packages in the environment.
–update-specs Update based on provided specifications.

Package Linking and Install-time Options:
–copy Install all packages using copies instead of hard- or
soft-linking.
–no-shortcuts Don’t install start menu shortcuts
–shortcuts-only SHORTCUTS_ONLY
Install shortcuts only for this package name. Can be
used several times.
-m, --mkdir --mkdir is pending deprecation and will be removed
in 25.3. Use conda create instead.
–clobber Allow clobbering (i.e. overwriting) of overlapping
file paths within packages and suppress related
warnings.

Networking Options:
-C, --use-index-cache
Use cache of channel index files, even if it has
expired. This is useful if you don’t want conda to
check whether a new version of the repodata file
exists, which will save bandwidth.
-k, --insecure Allow conda to perform “insecure” SSL connections and
transfers. Equivalent to setting ‘ssl_verify’ to
‘false’.
–offline Offline mode. Don’t connect to the Internet.

Output, Prompt, and Flow Control Options:
–json Report all output as json. Suitable for using conda
programmatically.
-v, --verbose Can be used multiple times. Once for detailed output,
twice for INFO logging, thrice for DEBUG logging, four
times for TRACE logging.
-q, --quiet Do not display progress bar.
-d, --dry-run Only display what would have been done.
-y, --yes Sets any confirmation values to ‘yes’ automatically.
Users will not be asked to confirm any adding,
deleting, backups, etc.
–download-only Solve an environment and ensure package caches are
populated, but exit prior to unlinking and linking
packages into the prefix.
–show-channel-urls Show channel urls. Overrides the value given by conda config --show show_channel_urls.

Examples:

Install the package ‘scipy’ into the currently-active environment::

conda install scipy

Install a list of packages into an environment, myenv::

conda install -n myenv scipy curl wheel

Install a specific version of ‘python’ into an environment, myenv::

conda install -p path/to/myenv python=3.11

(base) sibylles-mbp:~ sibyllestockli$ invest list
-bash: invest: command not found
(base) sibylles-mbp:~ sibyllestockli$