I confirm @pszynk's findings. I had to export CONDA_EXE and install python-libarchive-c. Note that _CONDA_ROOT is still referenced in /etc/fish/conf.d/conda.fish. (edit: I previously stated I didn't need to export)
Search Criteria
Package Details: python-conda 26.1.0-1
Package Actions
| 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.92 |
| First Submitted: | 2016-04-08 07:41 (UTC) |
| Last Updated: | 2026-02-07 17:14 (UTC) |
Dependencies (23)
- python
- python-archspecAUR
- python-boltonsAUR
- python-boto3 (python-boto3-gitAUR)
- python-botocore (python-botocore-gitAUR)
- python-conda-libmamba-solverAUR
- python-conda-package-handlingAUR
- python-frozendict
- python-packaging
- python-platformdirs
- python-pluggy
- python-pycosat
- python-requests
- python-ruamel-yaml (python-ruamel-yaml-hgAUR)
- python-setuptools-scm
- python-tqdm
- python-build (make)
- python-hatch-vcs (make)
- python-hatchling (python-hatchling-gitAUR) (make)
- python-installer (make)
- Show 3 more dependencies...
Required by (1)
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 Next › Last »
mdeff commented on 2019-07-01 10:25 (UTC) (edited on 2019-07-08 09:29 (UTC) by mdeff)
pszynk commented on 2019-06-28 11:54 (UTC) (edited on 2019-06-28 11:54 (UTC) by pszynk)
Also, there are two new dependecies
- python-libarchive-c
- python-tqdm
pszynk commented on 2019-06-28 11:41 (UTC) (edited on 2019-06-28 11:42 (UTC) by pszynk)
@bobschi yeah, there is an error in PKGBUILD, should be:
echo 'export CONDA_EXE=/usr/bin/conda
export CONDA_ROOT=/' | cat - conda/shell/etc/profile.d/conda.sh > conda.sh
wrong variables are exported! _CONDA_EXE and _CONDA_ROOT
cyrevolt commented on 2019-06-17 15:01 (UTC)
I guess it's somewhat related to https://github.com/conda/conda/commit/5efca40af360bdafdd78ada34b5bfd22137a3c8f - I'll see if I can find a fix. They are changing how paths and environments are being handled from time to time. That caused me a headache a few times already. :D
bobschi commented on 2019-06-17 09:48 (UTC)
After installing this package I manually have to add
export CONDA_EXE=/usr/bin/conda
to .bashrc, otherwise it won't work. Any ideas on that?
Stendec commented on 2019-06-14 17:56 (UTC)
There's a weird dependency circle with python-conda-package-handling when starting from scratch (neither python-conda or python-conda-package-handling installed). They both depend on each other and neither will build.
This can be circumvented by first installing python-conda-git, then python-conda-package-handling, and THEN python-conda, but this seems a little non-ideal.
cyrevolt commented on 2019-06-13 20:14 (UTC)
Please see the respective package: https://aur.archlinux.org/packages/python-conda-package-handling/#comment-696941
TL;DR: fixed
kristerv commented on 2019-06-13 10:50 (UTC) (edited on 2019-06-13 11:20 (UTC) by kristerv)
Install fails
==> Making package: python-conda-package-handling 1.3.4-1 (Thu 13 Jun 2019 01:47:01 PM EEST)
==> Retrieving sources...
-> Found 1.3.4.tar.gz
==> Validating source files with sha512sums...
1.3.4.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
Error downloading sources: python-conda-package-handling
just for info: https://aur.archlinux.org/packages/python-conda-git installs. edit: never mind, they don't include python-conda-package-handling.. also I'm now understanding the problem is with python-conda-package-handling and not python-conda - moving over.
mdeff commented on 2018-06-04 13:34 (UTC)
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.
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!