Package Details: miniconda3

Git Clone URL: (read-only, click to copy)
Package Base: miniconda3
Description: Mini version of Anaconda Python distribution
Upstream URL:
Keywords: anaconda conda python
Licenses: BSD-3-Clause
Provides: conda
Submitter: jadelord
Maintainer: carlosal1015
Last Packager: carlosal1015
Votes: 48
Popularity: 1.61
First Submitted: 2018-06-02 04:06 (UTC)
Last Updated: 2024-03-10 17:27 (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/ ] && source /opt/miniconda3/etc/profile.d/
  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 »

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?

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

nmstoker commented on 2023-08-16 00:22 (UTC) (edited on 2023-08-16 00:23 (UTC) by nmstoker)

I'm usually wary of using sudo with pip, and I found with a slight variation of @kearneyBack's method as below, you can run a non-sudo pip in the base conda env and get the cryptography and pyOpenSSL packages updated just fine:

$ conda activate base
(base) $ pip list | grep cryptography
cryptography            39.0.1
(base) $ pip install -U cryptography pyOpenSSL
Defaulting to user installation because normal site-packages is not writeable
Requirement already satisfied: cryptography in /opt/miniconda3/lib/python3.11/site-packages (39.0.1)
Collecting cryptography
  Downloading cryptography-41.0.3-cp37-abi3-manylinux_2_28_x86_64.whl (4.3 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 4.3/4.3 MB 8.0 MB/s eta 0:00:00
Requirement already satisfied: pyOpenSSL in /opt/miniconda3/lib/python3.11/site-packages (23.0.0)
Collecting pyOpenSSL
Downloading pyOpenSSL-23.2.0-py3-none-any.whl (59 kB)
  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 59.0/59.0 kB 7.7 MB/s eta 0:00:00
Requirement already satisfied: cffi>=1.12 in /opt/miniconda3/lib/python3.11/site-packages (from cryptography) (1.15.1)
Requirement already satisfied: pycparser in /opt/miniconda3/lib/python3.11/site-packages (from cffi>=1.12->cryptography) (2.21)
Installing collected packages: cryptography, pyOpenSSL
Successfully installed cryptography-41.0.3 pyOpenSSL-23.2.0
(base) $ pip list | grep cryptography
cryptography            41.0.3

From then on conda worked fine again.

carlosal1015 commented on 2023-08-11 12:25 (UTC)

Hi @busywhistling, yes conda 23.7.2 is available, but no available from here