Arch Linux User Repository

That's expected. The "base environment" is located under the /usr system directory and is not writable by users. That's because you installed conda system-wide with this package. If you'd instead installed it with e.g. the installer provided by continuum, the base environment would be situated under your home directory and you'd update with conda update conda.

Thank you. I switched back to the "base environment" just to test and I have the same error. Anyway, I trust you on the update through AUR so thanks again.

conda is not installed in your environment test01, but in the "base environment". If you installed conda with this package, there's no need for conda update conda though. You should update it with whatever AUR helper you're using.

Hi,

I just installed python-conda (fresh installation). When I run 'conda update conda', here is what I get. Thanks for your help!

$ conda update conda

PackageNotInstalledError: Package is not installed in prefix.
prefix: /home/$USER/.conda/envs/test01
package name: conda


(test01)

See the ouput of 'conda info -a':

$ conda info -a

    active environment : None
            shell level : 0
    user config file : /home/$USER/.condarc
populated config files : /home/$USER/.condarc
      conda version : 4.5.4
conda-build version : 3.10.5
     python version : 3.6.5.final.0
   base environment : /usr  (read only)
       channel URLs : <https://repo.anaconda.com/pkgs/main/linux-64>
                      <https://repo.anaconda.com/pkgs/main/noarch>
                      <https://repo.anaconda.com/pkgs/free/linux-64>
                      <https://repo.anaconda.com/pkgs/free/noarch>
                      <https://repo.anaconda.com/pkgs/r/linux-64>
                      <https://repo.anaconda.com/pkgs/r/noarch>
                      <https://repo.anaconda.com/pkgs/pro/linux-64>
                      <https://repo.anaconda.com/pkgs/pro/noarch>
                      <https://conda.anaconda.org/conda-forge/linux-64>
                      <https://conda.anaconda.org/conda-forge/noarch>
      package cache : /home/$USER/.conda/pkgs
   envs directories : /home/$USER/.conda/envs
                      /usr/envs
           platform : linux-64
         user-agent : conda/4.5.4 requests/2.18.4 CPython/3.6.5 Linux/4.16.13-1-ARCH arch/ glibc/2.27
            UID:GID : 1000:1000
         netrc file : None
       offline mode : False

# conda environments:
#
test01                *  /home/$USER/.conda/envs/test01
base                     /usr

sys.version: 3.6.5 (default, May 11 2018, 04:00:52) 
...
sys.prefix: /usr
sys.executable: /usr/bin/python3
conda location: /usr/lib/python3.6/site-packages/conda
conda-build: /usr/bin/conda-build
conda-convert: /usr/bin/conda-convert
conda-develop: /usr/bin/conda-develop
conda-env: /usr/bin/conda-env
conda-index: /usr/bin/conda-index
conda-inspect: /usr/bin/conda-inspect
conda-metapackage: /usr/bin/conda-metapackage
conda-render: /usr/bin/conda-render
conda-skeleton: /usr/bin/conda-skeleton
conda-verify: /usr/bin/conda-verify
user site dirs:

CIO_TEST: <not set>
CONDA_ROOT: /usr
CONDA_SHLVL: 0
MOZ_PLUGIN_PATH: /usr/lib/mozilla/plugins
PATH: /home/$USER/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
REQUESTS_CA_BUNDLE: <not set>
SSL_CERT_FILE: <not set>
WINDOWPATH: 1


WARNING: could not import _license.show_info
# try:
# $ conda install -n root _license

Add

pkgs_dirs:
  - ~/.conda/pkgs
envs_dirs:
  - ~/.conda/envs

to your ~/.condarc.

It should probably be reported upstream that the default paths should be relative to the user home, not relative to the base directory.

I'm having this issue when creating conda environment:

Solving environment: failed

NotWritableError: The current user does not have write permissions to a required path. path: /usr/pkgs/urls.txt uid: 1000 gid: 1000

If you feel that permissions on this path are set incorrectly, you can manually change them by executing

$ sudo chown 1000:1000 /usr/pkgs/urls.txt

In general, it's not advisable to use 'sudo conda'.

Sorry for the format :)

Great! Thanks for your work cyrevolt :)

For completeness, here's the content of the conda script as generated by the miniconda installer on one of my machines:

#!/home/user/miniconda3/bin/python

# -*- coding: utf-8 -*-
import re
import sys

from conda.cli import main

if __name__ == '__main__':
    sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0])
    sys.exit(main())

conda-env is the same, except that from conda.cli import main becomes from conda_env.cli.main import main (as you are doing in the PKGBUILD).

BTW completion is working perfectly for me on the fish shell. I don't think there's completion for any other shell though.

I have figured out how to get conda-env to work and it is now included. Enjoy! :)

Thank you for your suggestions mdeff!

1. I've looked into conda-env, and it is part of the main conda repo, and it is even being installed. I cannot find a conda-env executable file though. The README says even that it should be installed into the "base environment" by running: conda install -c conda conda-env I am not sure how this can be simply added to the package yet.

2. I a m not a csh user; I know setenv from fish, which appears to be just a compatibility thing and should actually be set -x, according to https://github.com/fish-shell/fish-shell/issues/2704 - it is the counterpart to bash's export, if I understand correctly. I am using it in the -git version of this package. I need to read more about this.

3. Well if we don't use setenv / set -x for zsh and fish, it makes sense to remove the export for bash also. It should be the same for all shells. I'll investigate.

4. Yup, I'm adding it. I am not sure yet though what the completion actually provides. I tried it out, but conda bu for example does not complete in neither shell. I opened a new terminal and even sourced the respective file again.

5. Awesome! I should also reach out to upstream to clarify packaging issues. The seemed to prefer the curl pipe sudo bash pattern to avoid/circumvent distro packaging so far. I hope they will be cooperative. :)