@chrisjbillington Another one using this package with sudo
.
You shouldn't do that and please create a clone if you want to modify the environment.
$ conda create -n myroot --clone /opt/anaconda
$ source activate myroot
$ conda install pyqt
Git Clone URL: | https://aur.archlinux.org/anaconda.git (read-only, click to copy) |
---|---|
Package Base: | anaconda |
Description: | Simplifies package management and deployment of Anaconda |
Upstream URL: | https://anaconda.com |
Licenses: | custom |
Provides: | conda |
Submitter: | flexiondotorg |
Maintainer: | carlosal1015 (petronny, AutoUpdateBot) |
Last Packager: | AutoUpdateBot |
Votes: | 111 |
Popularity: | 0.150582 |
First Submitted: | 2013-06-24 14:51 (UTC) |
Last Updated: | 2024-10-24 08:33 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 16 Next › Last »
@chrisjbillington Another one using this package with sudo
.
You shouldn't do that and please create a clone if you want to modify the environment.
$ conda create -n myroot --clone /opt/anaconda
$ source activate myroot
$ conda install pyqt
I really think Anaconda ought not to be an AUR package. It is a package manager and environment in its own right, and will leave files that are untracked by pacman, leading to advice elsewhere in this thread to install with --force to upgrade, and to clone the conda environment before installing packages. Neither of these are good ideas in the long run, as after an update or two to this AUR package, both will eventually break with files existing within the same directory that are for incompatible with each other with respect to compiler, Python version, or other things. You should install Anaconda exactly once (whether via this package or not) and then not update it from an AUR package, updating only with conda itself. Personally I would just put it in my home folder by running the installer from anaconda.org. pacman and the AUR add no extra value for this package, and it violates their assumptions of a package being a static set of files that can be upgraded.
it appears that anaconda is compiled w/o support for multiple processors. Is there a way for me to pass an argument like -j4
during install or anything. I have a 2-core 4-threads processor.
Anaconda3-5.3.0-Linux-x86_64.sh hash check failed.
@kbumsik @CaeZaR Build the package and install it with
$ pacman -U /path/to/anaconda.pkg.tar.xz --force
And you shouldn't use sudo conda
to install things to /opt/anaconda
.
Create a clone and use it.
$ conda create -n myroot --clone /opt/anaconda
$ source activate myroot
$ conda install pyqt
I have similar issues to @kbumsik when upgrading from 5.1.0 to 5.2.0.
All files report the following error:
anaconda: /opt/anaconda/XXX.XXX exists in filesystem
FYI, here is a desktop entry for anaconda-navigator, paste this to /usr/share/applications/anaconda-navigator.desktop
:
[Desktop Entry]
Version=1.0
Type=Application
Name=Anaconda-Navigator
GenericName=Anaconda
Comment=Scientific PYthon Development EnviRonment - Python3
Exec=bash -c 'source /opt/anaconda/bin/activate && anaconda-navigator'
Categories=Development;Science;IDE;Qt;Education;
Icon=python
Terminal=false
StartupNotify=true
MimeType=text/x-python;
I cannot upgrade from 5.1.0 -> 5.2.0 because it says some files already exists. It looks like it conflicts with some packages I installed using conda. Is there a workaround?
FYI, miniconda3 is now available in AUR, using a PKGBUILD nearly identical to the one used here.
Pinned Comments
mgd commented on 2024-08-08 11:19 (UTC)
I had to set CRYPTOGRAPHY_OPENSSL_NO_LEGACY=true in the environment to start Anaconda. While this is easy to research it might be helpful to add this by default or at least emit a note stating that.
carlosal1015 commented on 2022-09-03 23:07 (UTC) (edited on 2023-07-15 17:00 (UTC) by carlosal1015)
Important note: This is the way how to upgrade.
Suppose that we have this line in
~/.bashrc
or~/.zshrc
or etc.Changelog: https://docs.anaconda.com/free/anaconda/reference/release-notes
petronny commented on 2020-08-19 10:36 (UTC) (edited on 2023-12-12 12:23 (UTC) by petronny)
This PKGBUILD is tested with
extra-x86_64-build
.If you get any problem when build this package, you can try the prebuilt binary from the arch4edu repository. It's also built with
extra-x86_64-build
.