Arch Linux User Repository

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

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.

That sounds like it would be a security issue. Users shouldn't randomly be able to write to system files like /opt/miniconda3.

Hello, everyone. I try to conda install -c conda-forge jupyterlab but I got this

EnvironmentNotWritableError: The current user does not have write permissions to the target environment.
  environment location: /opt/miniconda3
  uid: 1000
  gid: 1000

then I add sudo then it work. why not just give the user higher privilege to this package(/opt/miniconda3)? For safety or something else?

From the new PKGBUILD's git diff, I see the versio and sha256sums changed. But as jadelord said, he or she will disown this pkg.The Maintainer still is Ashwin Vishnu <ashwinvis+arch At protonmail DoT cOm>. But from this web page, it writes Maintainer: Ta180m. So it is a manner to keep the Ta180m's position or just something else?

@jadelord, I didn't update conda package in the base environment. I need to use the makepkg method posted by @JcNils and still complains, so, had to:

yay -R miniconda3
sudo rm -rf /opt/miniconda3

and then,

makepkg -sric 

@OvelixMax, did you ever manually update the conda package in the base environment. Doing so without using package manager might have led to conflicts. Try installing using makepkg and if it still complains, you need to do a clean reinstallation.

Archlinux user here. I can't update miniconda 4.9.2 with python 3.9 using yay.

error: failed to commit transaction (conflicting files)
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda-4.9.2-py3.8.egg-info/PKG-INFO exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda-4.9.2-py3.8.egg-info/SOURCES.txt exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda-4.9.2-py3.8.egg-info/dependency_links.txt exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda-4.9.2-py3.8.egg-info/entry_points.txt exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda-4.9.2-py3.8.egg-info/not-zip-safe exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda-4.9.2-py3.8.egg-info/requires.txt exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda-4.9.2-py3.8.egg-info/top_level.txt exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda/_vendor/tqdm/__pycache__/asyncio.cpython-38.pyc exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda/_vendor/tqdm/__pycache__/auto.cpython-38.pyc exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda/_vendor/tqdm/__pycache__/cli.cpython-38.pyc exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda/_vendor/tqdm/__pycache__/std.cpython-38.pyc exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda/_vendor/tqdm/__pycache__/utils.cpython-38.pyc exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda/_vendor/tqdm/asyncio.py exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda/_vendor/tqdm/auto.py exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda/_vendor/tqdm/cli.py exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda/_vendor/tqdm/contrib/__init__.py exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda/_vendor/tqdm/contrib/__pycache__/__init__.cpython-38.pyc exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda/_vendor/tqdm/contrib/__pycache__/concurrent.cpython-38.pyc exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda/_vendor/tqdm/contrib/__pycache__/itertools.cpython-38.pyc exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda/_vendor/tqdm/contrib/concurrent.py exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda/_vendor/tqdm/contrib/itertools.py exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda/_vendor/tqdm/std.py exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda/_vendor/tqdm/utils.py exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda/cli/__pycache__/main_compare.cpython-38.pyc exists in filesystem
miniconda3: /opt/miniconda3/lib/python3.8/site-packages/conda/cli/main_compare.py exists in filesystem
Errors occurred, no packages were upgraded.

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