| 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 (Rin4th) |
| Last Packager: | carlosal1015 |
| Votes: | 59 |
| Popularity: | 2.28 |
| First Submitted: | 2018-06-02 04:06 (UTC) |
| Last Updated: | 2026-05-02 18:36 (UTC) |
Latest version 26.1.1.1-1 fails to upgrade and ends with the error message,
.cache/yay/miniconda3/miniconda3-26.1.1.1-1-x86_64.pkg.tar.zst] - exit status 1
Purging any remnants of the failed install and going back to the previous 25.11.1.1-1 version works as expected.
Please take my patch that bumps to 26.1.1.1: https://github.com/lubosz/miniconda3/commit/7b9231881ef279b4fb0959a3b99aa761a7d261b7
The current PKGBUILD for miniconda3 25.5.1.1-1 still calls the py312 installer inside package(), while the source array has already been updated to py313:
Because the py312 file is no longer downloaded, the build fails with:
bash: /home/$USER/.cache/paru/clone/miniconda3/src/Miniconda3-py312_25.5.1-1-Linux-x86_64.sh: No such file or directory ==> ERROR: A failure occurred in package().
Simply replacing py312 with py313 in the installer path resolves the issue;
bash: /home/simona/.cache/yay/miniconda3/src/Miniconda3-py312_25.5.1-1-Linux-x86_64.sh: File o directory non esistente
it gives this error :
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.)
the solution is to put this : " export CRYPTOGRAPHY_OPENSSL_NO_LEGACY='1' " into /etc/profile.d/conda.sh
thank you so much
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?
Pinned Comments
carlosal1015 commented on 2024-07-10 02:47 (UTC)
In order to check a new version
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
~/.bashrcor~/.zshrcor etc.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.