Package Details: python-conda 26.1.0-1

Git Clone URL: https://aur.archlinux.org/python-conda.git (read-only, click to copy)
Package Base: python-conda
Description: OS-agnostic, system-level binary package manager and ecosystem https://conda.io
Upstream URL: https://github.com/conda/conda
Licenses: BSD-3-Clause
Conflicts: python-conda-git
Provides: python-conda-env
Submitter: cyrevolt
Maintainer: flying-sheep
Last Packager: flying-sheep
Votes: 35
Popularity: 0.24
First Submitted: 2016-04-08 07:41 (UTC)
Last Updated: 2026-02-07 17:14 (UTC)

Pinned Comments

flying-sheep commented on 2025-01-06 13:01 (UTC)

You forgot to rebuild all your AUR python packages after that update. That's a necessary step and has nothing to do with our conda package.

See e.g. https://www.reddit.com/r/archlinux/comments/1hk2wii/comment/m3g11xz/

Please ask in the Arch BBS or on e.g. Reddit if you have further questions!

Latest Comments

1 2 3 4 5 6 .. 12 Next › Last »

flying-sheep commented on 2025-12-29 20:14 (UTC)

Indeed, thanks! I fixed python-conda-libmamba-solver’s deps!

mikeblake commented on 2025-12-29 03:43 (UTC)

Hello. I was getting error after install to Python 3.13.11 environment:

Error while loading conda entry point: conda-libmamba-solver (No module named 'msgpack')

After installing python-msgpack from repo all is well now. Did not run into it anywhere as a dependency until I tried to run conda. Hopefully this is helpful feedback. Thank you maintainer(s) (=^.^=).

flying-sheep commented on 2025-11-19 17:07 (UTC) (edited on 2025-11-19 17:08 (UTC) by flying-sheep)

Totally expected. The dependencies in question are required by libmamba (part of the micromamba package). So rebuild that against what you have on your system and you’re fine.

This is the AUR, which doesn’t have binary packages, so if you use stuff from here, you’re responsible for rebuilding things once system libraries update and packages you built yourself are no longer linking against something valid.

acud commented on 2025-11-19 16:20 (UTC)

This doesn't work out-of-the box. First thing is that it looks for outdated dependencies (libfmt.so.11, libsimdjson.so.26). After symlinking them to newer versions I'm getting this: Error while loading conda entry point: conda-libmamba-solver (/usr/lib/libmamba.so.4: undefined symbol: _ZN3fmt3v116detail12is_printableEj). Not sure if this is expected behavior or not.

flying-sheep commented on 2025-09-02 10:16 (UTC) (edited on 2025-09-02 10:20 (UTC) by flying-sheep)

@mets.web: I fixed the micromamba build, should work now.

@brianrobt: python-conda-libmamba-solver is actually a mandatory dependency as an unconfigured conda will try to use it and break, so please don’t remove it from the dependency list again.

mets.web commented on 2025-07-20 11:14 (UTC)

error: packages failed to build: micromamba-2.3.0-1 python-conda-25.5.1-1

brianrobt commented on 2025-01-24 15:16 (UTC)

@vlovich, see the post I just pinned.

vlovich commented on 2025-01-24 14:55 (UTC)

After an update, I'm getting ModuleNotFoundError: No module named 'boltons' trying to run conda:

Traceback (most recent call last):
  File "/usr/lib/python3.13/site-packages/conda/exception_handler.py", line 18, in __call__
    return func(*args, **kwargs)
  File "/usr/lib/python3.13/site-packages/conda/cli/main.py", line 28, in main_subshell
    from ..base.context import context
  File "/usr/lib/python3.13/site-packages/conda/base/context.py", line 26, in <module>
    from boltons.setutils import IndexedSet
ModuleNotFoundError: No module named 'boltons'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/conda", line 8, in <module>
    sys.exit(main())
             ~~~~^^
  File "/usr/lib/python3.13/site-packages/conda/cli/main.py", line 105, in main
    return conda_exception_handler(main, *args, **kwargs)
  File "/usr/lib/python3.13/site-packages/conda/exception_handler.py", line 386, in conda_exception_handler
    return_value = exception_handler(func, *args, **kwargs)
  File "/usr/lib/python3.13/site-packages/conda/exception_handler.py", line 21, in __call__
    return self.handle_exception(exc_val, exc_tb)
           ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.13/site-packages/conda/exception_handler.py", line 52, in handle_exception
    from .exceptions import (
    ...<3 lines>...
    )
  File "/usr/lib/python3.13/site-packages/conda/exceptions.py", line 20, in <module>
    from .auxlib.entity import EntityEncoder
  File "/usr/lib/python3.13/site-packages/conda/auxlib/entity.py", line 246, in <module>
    from boltons.timeutils import isoparse
ModuleNotFoundError: No module named 'boltons'

bcb commented on 2025-01-22 16:31 (UTC)

Yes, the new version successfully installed.

It may be that GitHub don't guarantee patches will always get the same hash. Either of those downloaded patches would successfully apply to the code, its only an issue when using the hashsum for integrity checking. When I'll get a chance I'll see if its mentioned in any documentation, and otherwise report it (or post in the community discussions) to get some clarification.

brianrobt commented on 2025-01-22 16:20 (UTC)

Thanks for digging into that @bcb! Were you able to install the new version successfully?

As for the GitHub issue with shortening the commit hash in the patch, that is an interesting bug. I've never seen that before either, and we probably aren't the only ones who have or will experience it. If you want to report it to GitHub, you can use this link to open a ticket: https://support.github.com/contact/bug-report

1 2 3 4 5 6 .. 12 Next › Last »