Package Details: python-conda 26.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-3-Clause
Conflicts: python-conda-git
Provides: python-conda-env
Submitter: cyrevolt
Maintainer: flying-sheep
Last Packager: flying-sheep
Votes: 36
Popularity: 0.94
First Submitted: 2016-04-08 07:41 (UTC)
Last Updated: 2026-02-07 17:14 (UTC)

Pinned Comments

flying-sheep commented on 2025-01-06 13:01 (UTC)

You forgot to rebuild all your AUR python packages after that update. That's a necessary step and has nothing to do with our conda package.

See e.g. https://www.reddit.com/r/archlinux/comments/1hk2wii/comment/m3g11xz/

Please ask in the Arch BBS or on e.g. Reddit if you have further questions!

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 Next › Last »

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! :)

cyrevolt commented on 2018-02-19 00:12 (UTC)

I am sorry for fish users. Version 4.4 changed the shell integration again.

After conda activate, you cannot use conda anymore. It will raise the error ImportError: No module named 'conda'. If anyone has a solution, I'd be happy to know - and everyone else surely. :) To get this to work at all, I had to inject the path to the /usr/bin/conda script into the fish script that has to be sourced. And that one actually reads "# WARNING: Not a real conda entry point. Do not use other than for tests.".

cyrevolt commented on 2017-11-24 11:16 (UTC)

Thanks everyone here for letting me know about updates! With the most recent bump, I also updated the other conda tools, i.e., conda-verify and conda-build. They both made major changes from v2 to v3. :)

cyrevolt commented on 2017-05-07 20:52 (UTC)

I have now switched to using the stable python-ruamel-yaml from the community repo and updated to 4.3.17. I also read that 4.4 should be released somewhat soon. I hope everything is fine now. :)

cyrevolt commented on 2017-04-26 22:45 (UTC)

Please discuss this at https://aur.archlinux.org/packages/python-ruamel.yaml-hg/ @ardeaf I'm not much familiar with Mercurial, but I would suggest to try checking out an older revision when building, i.e. adjusting the PKGBUILD for it.

ardeaf commented on 2017-04-26 22:34 (UTC) (edited on 2017-04-26 22:35 (UTC) by ardeaf)

Can't build python-ruamel.yaml-hg: :: Proceed with installation? [Y/n] y :: Retrieving package(s)... :: python-conda build files are up-to-date -- skipping :: python-ruamel.yaml-hg build files are up-to-date -- skipping [sudo] password for ardeaf: :: Checking python-ruamel.yaml-hg integrity... ==> Making package: python-ruamel.yaml-hg 0.12.14.r1.486262651aa3-1 (Wed Apr 26 12:33:27 HST 2017) ==> Retrieving sources... -> Updating yaml hg repo... pulling from https://bitbucket.org/ruamel/yaml searching for changes no changes found ==> Validating source files with md5sums... yaml ... Skipped :: Checking python-conda integrity... ==> Making package: python-conda 4.3.6-1 (Wed Apr 26 12:33:31 HST 2017) ==> Retrieving sources... -> Found 4.3.6.tar.gz ==> Validating source files with sha512sums... 4.3.6.tar.gz ... Passed :: Building python-ruamel.yaml-hg package(s)... ==> Making package: python-ruamel.yaml-hg 0.14.10.r1.79122dcec309-1 (Wed Apr 26 12:33:32 HST 2017) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> WARNING: Using existing $srcdir/ tree ==> Starting pkgver()... ==> Removing existing $pkgdir/ directory... ==> Entering fakeroot environment... ==> Starting package()... /usr/lib/python3.6/site-packages/pip/commands/install.py:194: UserWarning: Disabling all use of wheels due to the use of --build-options / --global-options / --install-options. cmdoptions.check_install_build_global(options) Directory '.' is not installable. File 'setup.py' not found. ==> ERROR: A failure occurred in package(). Aborting... :: Building python-conda package(s)... ==> Making package: python-conda 4.3.6-1 (Wed Apr 26 12:33:34 HST 2017) ==> Checking runtime dependencies... ==> Installing missing dependencies... error: target not found: python-ruamel.yaml-hg ==> ERROR: 'pacman' failed to install missing dependencies. :: failed to build python-ruamel.yaml-hg package(s) :: failed to build python-conda package(s)

confusedfla commented on 2017-01-30 07:57 (UTC)

What's the reason for depending on python-ruamel.yaml-hg? python-ruamel.yaml is now in community: https://www.archlinux.org/packages/community/x86_64/python-ruamel-yaml/

cyrevolt commented on 2017-01-24 22:49 (UTC)

The issue is now "fixed", using a "testing" installation as they mention it in `setup.py`. I hope this causes no other side-effects. Please let me know if this works for you now! :)

jddantes commented on 2017-01-20 04:48 (UTC)

Seems conda wasn't installed using that commit. Listed the details here (https://bbs.archlinux.org/viewtopic.php?pid=1685147#p1685147)

cyrevolt commented on 2017-01-10 23:11 (UTC) (edited on 2017-01-10 23:17 (UTC) by cyrevolt)

Sorry for this issue, and thanks to geno_whirl for pointing it out (see https://bbs.archlinux.org/viewtopic.php?id=221775 ). Upstream has made some changes which essentially doesn't create the binaries conda, activate and deactivate anymore. When you run the setup.py manually, you will see this message: WARNING: Your current install method for conda only supports conda as a python library. You are not installing a conda executable command or activate/deactivate commands. If your intention is to install conda as a standalone application, currently supported install methods include the Anaconda installer and the miniconda installer. This only affects you if you are using a POSIX shell like bash. If you run fish (like I do ;)), you will still be able to use conda. :) To fix it, you can downgrade by running the following: git clone "https://aur.archlinux.org/python-conda.git" cd python-conda git checkout 8e0dfd4c6621e5ad64d5debc2c2b743e3c452059 makepkg -i That clones the git repo from AUR, checks out the commit with the older version v4.2.12-3, and builds and installs it.