Arch Linux User Repository

In order to check a new version

$ git clone https://aur.archlinux.org/miniconda3.git
$ cd miniconda3
$ nvchecker -c .nvchecker.toml                        
[I 07-09 21:47:02.603 core:416] miniconda3: updated to 24.5.0.0

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.

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

In order to check a new version

$ git clone https://aur.archlinux.org/miniconda3.git
$ cd miniconda3
$ nvchecker -c .nvchecker.toml                        
[I 07-09 21:47:02.603 core:416] miniconda3: updated to 24.5.0.0

Not necessarily related to the AUR package, but any packages installed through miniconda relying on Qt fail with

Could not find the Qt platform plugin "xcb" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Any idea what might be going on?

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 ?

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

Thanks, now should be fixed.

The line 28 of PKGBUILD should be:

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

since source use pkgver instead of _pkgver.

Hello, can this repo add the aarch64 platform support?

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

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

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.

Hi @joanmanel, could you look

$ env

and look if any CONDA_FOO environment variable is activated?