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.
Search Criteria
Package Details: python-conda 23.1.0-1
Git Clone URL: | https://aur.archlinux.org/python-conda.git (read-only, click to copy) |
---|---|
Package Base: | python-conda |
Description: | OS-agnostic, system-level binary package manager and ecosystem https://conda.io |
Upstream URL: | https://github.com/conda/conda |
Licenses: | BSD |
Provides: | python-conda, python-conda-env |
Submitter: | cyrevolt |
Maintainer: | iyanmv |
Last Packager: | specter119 |
Votes: | 29 |
Popularity: | 0.68 |
First Submitted: | 2016-04-08 07:41 (UTC) |
Last Updated: | 2023-03-02 04:36 (UTC) |
Dependencies (8)
Required by (3)
Sources (1)
mdeff commented on 2018-06-04 11:51 (UTC)
Pixys commented on 2018-06-02 05:45 (UTC) (edited on 2018-06-03 02:25 (UTC) by Pixys)
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
mdeff commented on 2018-05-11 12:14 (UTC)
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.
tr3s commented on 2018-05-10 22:25 (UTC)
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 :)
mdeff commented on 2018-05-02 15:35 (UTC) (edited on 2018-05-02 15:40 (UTC) by mdeff)
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.
cyrevolt commented on 2018-05-02 00:13 (UTC)
I have figured out how to get conda-env
to work and it is now included. Enjoy! :)
cyrevolt commented on 2018-04-04 08:23 (UTC) (edited on 2018-04-04 08:33 (UTC) by cyrevolt)
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. :)
mdeff commented on 2018-03-28 17:40 (UTC) (edited on 2018-03-28 17:41 (UTC) by mdeff)
I've spotted some issues with that package:
/usr/bin/conda-env
is not installed. I guess this file (along with/usr/bin/conda
) is generated by the installer. Withoutconda-env
users cannot access theconda env
commands, e.g.conda env export
.- Does the csh shell needs
setenv
instead ofset
? (installer usessetenv
) - The bash shell does not need
export
(the variable can stay private, as done by the installer) - Similarly to
_CONDA_EXE
,_CONDA_ROOT
should be set to/
. For fish,set _CONDA_ROOT /
(it is used for auto-completion). - I've submitted a PR to auto-complete
conda env
in fish (https://github.com/conda/conda/pull/7101).
cyrevolt commented on 2018-02-21 21:18 (UTC)
The issues are now fixed and it works again. :) I tested with bash, fish, and zsh.
You may need to set pkgs_dirs
in your condarc
. To do so, you can use the CLI: https://github.com/conda/conda/blob/caedbbfe37860f3b61466408cc9ae199b3ffe910/CHANGELOG.md#4315-2017-03-20
Thanks everyone for helping and enjoy conda! :)
Pinned Comments
cyrevolt commented on 2020-12-14 23:01 (UTC) (edited on 2020-12-14 23:18 (UTC) by cyrevolt)
Errors
If you see something like this, the "error" is that AUR packages are not rebuilt when the system Python version is upgraded, which just happened again with 3.9. You need to manually upgrade each and every Python package from AUR, unfortunately. That is quite a caveat, because not everyone notices that something specific like Python is upgraded when they run
pacman -Syu
and see a list of 200 or more packages. This also happens with Node.js and what not.Solution
So I have just bumped the package here as well as
python-conda-build
, which triggers updates with e.g.yay -Su
. However, some dependencies may not have a new version now. What we could do for this case is to increasepkgrel
for those other packages. It feels hacky, but at least it works.Addendum
I am sorry for the inconvenience. Now the remaining problem is: Because of the bunch of dependencies and dependencies of dependencies, it is easy to miss one of them. =) Secondly, I do not own all the dependencies, so some will need manual maintenance either way, unfortunately. For example, you will need to reinstall
python-glob2-git
. Please let us know here if anyone of you runs into issues and we will try to help.Notes
To rebuild, you need to pass the
--rebuild
option.Example:
yay -S python-glob2-git --rebuild