As for a python prefix, I'm more inclined to see anaconda as something different from python that uses python (something like `visit`). Unless it really is a problem, I don't see a point in changing that yet
Search Criteria
Package Details: anaconda 2024.10.1-1
Package Actions
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: | 110 |
Popularity: | 0.092538 |
First Submitted: | 2013-06-24 14:51 (UTC) |
Last Updated: | 2024-10-24 08:33 (UTC) |
Dependencies (14)
- alsa-lib (optional) – for Anaconda Navigator support
- libglvnd (libglvnd-gitAUR) (optional) – for Anaconda Navigator support
- libxau (optional) – for Anaconda Navigator support
- libxcomposite (optional) – for Anaconda Navigator support
- libxcursor (optional) – for Anaconda Navigator support
- libxdamage (optional) – for Anaconda Navigator support
- libxfixes (optional) – for Anaconda Navigator support
- libxi (libxi-gitAUR) (optional) – for Anaconda Navigator support
- libxrandr (libxrandr-gitAUR) (optional) – for Anaconda Navigator support
- libxrender (optional) – for Anaconda Navigator support
- libxss (optional) – for Anaconda Navigator support
- libxtst (optional) – for Anaconda Navigator support
- mesa (mesa-minimal-gitAUR, mesa-gitAUR, mesa-wsl2-gitAUR, amdonly-gaming-mesa-gitAUR, mesa-amd-bc250AUR, mesa-amber) (optional) – for Anaconda Navigator support
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-mimeoAUR, mimejs-gitAUR) (optional) – for
Required by (1)
- python-conda-pack (requires conda)
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 Next › Last »
immae commented on 2015-04-06 16:45 (UTC)
immae commented on 2015-04-06 16:41 (UTC)
It's up to date now with 2.2.0
@atczaja: I have the same (somehing.so == libfakeroot.so), I don't know where it comes from. It does work however on my machine, even though the errors are there.
@183.amir: added libtool
183.amir commented on 2015-04-05 09:48 (UTC)
Please consider adding "libtool" to the options. I was facing a bug because the ".la" files were removed during packaging. Link to the bug: https://github.com/conda/conda/issues/1248
atczaja commented on 2015-04-01 19:58 (UTC)
When installing this package, I get a ton of "ERROR: ld.so: object 'something.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored". Even after letting the installation process finish despite these errors, I cannot get Anaconda to work. I've tried installing with pacaur as well as building from the tarball and makepkg. Is anyone else getting this problem, or is there something I'm doing wrong?
davidovitch commented on 2015-02-11 18:36 (UTC)
Regarding the name: (python-)anaconda. I noticed that the other python distribution packages, such as python2-epd-oss and python2-ets (Enthought), or python-xy, are indeed a collection of packages installed in the system's python environment. So although I agree it can be confusing for some, this package is clearly not a python package, but an independent python installation.
On the other hand, the python prefix is also used just to indicate that the package contains python code/programs...
TLDR: to "python-" prefix, or not to "python-" prefix, that is the question...
immae commented on 2015-01-06 16:32 (UTC)
@tinyprog: to me python-anaconda would be a python (3) module, while here anaconda is a complete and self-sufficient (python) distribution.
But maybe I missinterpreted the meaning of "python-" prefix.
limadm commented on 2015-01-06 01:21 (UTC)
Why not "python-anaconda" and "python2-anaconda"?
immae commented on 2014-11-12 23:35 (UTC)
Package updated.
Please note that this is now the package for version 3.4 of python, according to naming conventions for Archlinux. For version 2.7 of python, use https://aur.archlinux.org/packages/anaconda2/
which I'm also maintaining
ghatanothoa commented on 2014-10-17 19:27 (UTC)
hey hey, so I'm getting:
.
.
.
installing: scipy-0.14.0-np18py27_0 ...
==> ERROR: A failure occurred in package().
Aborting...
==> ERROR: Makepkg was unable to build anaconda.
I had problems before this with it filling up /tmp but sorted that by adding a gb to it in fstab. Any ideas on what is going wrong now? Not the most helpful of error messages.
marekpetrik commented on 2014-09-03 11:56 (UTC)
I second immae's comment. I would expect anaconda to be python3 based and anaconda2 to be python2 based. I would use python 3.
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
.