Package Details: miniconda3 24.3.0.0-4

Git Clone URL: https://aur.archlinux.org/miniconda3.git (read-only, click to copy)
Package Base: miniconda3
Description: Mini version of Anaconda Python distribution
Upstream URL: https://conda.io/en/latest/miniconda
Keywords: anaconda conda python
Licenses: BSD-3-Clause
Provides: conda
Submitter: jadelord
Maintainer: carlosal1015
Last Packager: carlosal1015
Votes: 50
Popularity: 2.49
First Submitted: 2018-06-02 04:06 (UTC)
Last Updated: 2024-04-27 21:00 (UTC)

Pinned Comments

carlosal1015 commented on 2022-05-26 20:15 (UTC) (edited on 2022-05-26 20:15 (UTC) by carlosal1015)

Important note: This is the way how to upgrade.

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

[ -f /opt/miniconda3/etc/profile.d/conda.sh ] && source /opt/miniconda3/etc/profile.d/conda.sh
  1. Before to upgrade I comment this line.
  2. Upgrade the package as usual.
  3. Uncomment the line.

jadelord commented on 2021-02-05 09:50 (UTC) (edited on 2022-02-03 11:32 (UTC) by jadelord)

I have packaged micromamba in AUR. Try it if you are looking for a lightweight, barebones alternative to miniconda.

Latest Comments

1 2 3 4 5 6 7 Next › Last »

feiticeir0 commented on 2024-05-18 21:41 (UTC) (edited on 2024-05-18 21:42 (UTC) by feiticeir0)

I'm getting an error while using conda, that the only solution I've found is, before installing packages I have to:

export CRYPTOGRAPHY_OPENSSL_NO_LEGACY=1

Because, otherwise, I get this:

Error while loading conda entry point: conda-content-trust (OpenSSL 3.0's legacy provider failed to load. This is a fatal error by default, but cryptography supports running without legacy algorithms by setting the environment variable CRYPTOGRAPHY_OPENSSL_NO_LEGACY. If you did not expect this error, you have likely made a mistake with your OpenSSL configuration.

What could it be ?

tixwho commented on 2024-04-27 19:18 (UTC)

Line 28 of PKGBUILD should be changed from Miniconda3-py311 to Miniconda3-py312 accordingly?

carlosal1015 commented on 2024-03-10 17:28 (UTC)

Thanks, now should be fixed.

chust commented on 2024-03-10 17:01 (UTC)

The line 28 of PKGBUILD should be:

  bash "${srcdir}/${pkgname}-${pkgver}-${CARCH}.sh" -b -p ${prefix} -f

since source use pkgver instead of _pkgver.

rainbus commented on 2023-12-07 07:35 (UTC)

Hello, can this repo add the aarch64 platform support?

https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-aarch64.sh

raisinbl commented on 2023-11-02 08:04 (UTC)

@weker01 my work around is to rm /opt/miniconda3 -rf to remove conflict and install again, remember move your essential config to somewhere else before that.

weker01 commented on 2023-10-30 22:20 (UTC)

I have a similar problem as @joanmanel and have no CONDA_* variables in env... but it is not "/opt/miniconda3/pkgs/" but "/opt/miniconda3/lib/python3.11/site-packages/" where the conflicts lie.

I also manually activate conda, so there is no need to uncomment any lines, and conda is deactivated.

carlosal1015 commented on 2023-10-28 15:44 (UTC)

Hi @joanmanel, could you look

$ env

and look if any CONDA_FOO environment variable is activated?

joanmanel commented on 2023-10-28 09:01 (UTC)

Hi there. Went to update the package (through yay). I uncommented the line in bashrc as suggested. But I went a bunch of

miniconda: /opt/miniconda3/pkgs/.... exists in filesystem

1 2 3 4 5 6 7 Next › Last »