Arch Linux User Repository

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.

Important note: This is the way how to upgrade.

Suppose that we have this line in ~/.bashrc or ~/.zshrc or etc.

[ -f /opt/anaconda/etc/profile.d/conda.sh ] && source /opt/anaconda/etc/profile.d/conda.sh

1. Before to upgrade I comment this line.
2. Upgrade the package as usual.
3. Uncomment the line.

Changelog: https://docs.anaconda.com/free/anaconda/reference/release-notes

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.

@petronny I try to upgrade to 2019.07. during build package, it report:

Unpacking payload ... [7559] mod is NULL - structTraceback (most recent call last): File "/spare/local/nwani/pyinstaller_stuff/dev/lib/python3.6/struct.py", line 13, in <module> ModuleNotFoundError: No module named '_struct' [7559] mod is NULL - pyimod02_archiveTraceback (most recent call last): File "/spare/local/nwani/pyinstaller_stuff/dev/lib/python3.6/site-packages/PyInstaller/loader/pyimod02_archive.py", line 28, in <module> ModuleNotFoundError: No module named 'struct' [7559] mod is NULL - pyimod03_importersTraceback (most recent call last): File "/spare/local/nwani/pyinstaller_stuff/dev/lib/python3.6/site-packages/PyInstaller/loader/pyimod03_importers.py", line 24, in <module> ModuleNotFoundError: No module named 'pyimod02_archive' Traceback (most recent call last): File "site-packages/PyInstaller/loader/pyiboot01_bootstrap.py", line 15, in <module> ModuleNotFoundError: No module named 'pyimod03_importers' [7559] Failed to execute script pyiboot01_bootstrap ERROR: could not extract tar starting at offset 000000000000020980+9231072+2

the package's sha256sum is good.

I've upgraded this package to 2019.07.

But I have to say the anaconda project really s***s. They removed the old good .install.py and I have to make the build very dirty. I can't guarantee all things functional now.

Someday we may need to drop this package from AUR forever.

@bergentroll ok, I'll fix it in the next release.

petronny, that's right, but it is still OK to point BSD license: https://wiki.archlinux.org/index.php/PKGBUILD#license. E.g.: https://www.archlinux.org/packages/community/x86_64/bsd-games/. This way seems rather more informative.

@bergentroll custom means it doesn't match any license in /usr/share/licenses/common. So it's fine.

Why custom license? Isn't it under 3-clause BSD? https://docs.anaconda.com/anaconda/eula/

I'm not using it with sudo, in fact I'm not using it at all, I'm just opinionated.

But I tested what I thought would break and it's not as bad as I thought.

Because cloning really does make basically a new installation, upgrading Anaconda via the AUR does not mess with the existing clone. Though it would still make me wary.

Also, making a clone is essentially a completely separate installation not tracked by pacman, one which will not be updated when the AUR package updates. So it doesn't break, but you're also not gaining anything from using a package manager. It's even in your home directory (I didn't realise this).

Ok, maybe it's not so bad having this as an AUR package. It is still pretty odd, but I can see it might be a good workflow for some.

@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.