Package Details: micromamba 2.8.1-1

Git Clone URL: https://aur.archlinux.org/micromamba.git (read-only, click to copy)
Package Base: micromamba
Description: The fast cross-platform package manager
Upstream URL: https://github.com/mamba-org/mamba
Licenses: BSD-3-Clause
Conflicts: micromamba-bin
Provides: libmamba, python-libmambapy
Submitter: gdolle
Maintainer: carlosal1015 (flying-sheep)
Last Packager: carlosal1015
Votes: 10
Popularity: 0.022853
First Submitted: 2021-03-21 15:23 (UTC)
Last Updated: 2026-06-12 03:27 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

flying-sheep commented on 2025-07-25 11:22 (UTC) (edited on 2025-07-25 11:33 (UTC) by flying-sheep)

the issues are because of pybind11 3.0: https://github.com/mamba-org/mamba/issues/4024

with pybind11 2.x installed, we just need to modify package() to have a cd ${_pkgname}-${pkgver} before the install -Dm 644 LICENSE … and everything works:

paru -Qlq micromamba | treeify 
[/]
 └─usr
    ├─bin/mamba
    ├─etc/profile.d/mamba.sh
    ├─include/mamba/**.hpp
    ├─lib
    │  ├─cmake/libmamba/*.cmake
    │  ├─libmamba.so
    │  ├─libmamba.so.4
    │  ├─libmamba.so.4.0.1
    │  └─python3.13
    │     └─site-packages
    │        ├─libmambapy/**.py
    │        └─libmambapy-2.3.0.dist-info
    │           ├─METADATA
    │           ├─RECORD
    │           ├─WHEEL
    │           ├─licenses
    │           │  └─LICENSE
    │           └─top_level.txt
    └─share/licenses/micromamba/LICENSE.txt

carlosal1015 commented on 2025-07-23 17:11 (UTC)

I see many errors like that, could you try fix @flying-sheep

FAILED: libmambapy/CMakeFiles/bindings.dir/src/libmambapy/bindings/utils.cpp.o

carlosal1015 commented on 2025-07-23 16:10 (UTC)

Thanks, I agree that if wheels are available, let's follow https://wiki.archlinux.org/title/Python_package_guidelines#Standards_based_(PEP_517)

But I do not modify cmake flags.

flying-sheep commented on 2025-07-23 11:44 (UTC) (edited on 2025-07-23 11:45 (UTC) by flying-sheep)

you’re installing libmambapy wrong. you need to install the package metadata too.

otherwise conda fails on startup with

importlib.metadata.PackageNotFoundError: No package metadata was found for libmambapy

When I built it, I used the following, maybe that helps

build() {
  cd "$srcdir/$_name"

  cmake -S. -Bbuild \
    -DCMAKE_BUILD_WITH_INSTALL_RPATH=ON \
    -DBUILD_LIBMAMBA=ON \
    -DBUILD_LIBMAMBAPY=ON \
    -DBUILD_MICROMAMBA=OFF \
    -DBUILD_MAMBA_PACKAGE=OFF \
    -DBUILD_SHARED=ON
  cmake --build build --parallel 8
  cmake --install build --prefix install

  cd libmambapy
  export SKBUILD_CONFIGURE_OPTIONS="\
      -DCMAKE_BUILD_WITH_INSTALL_RPATH=ON \
      -DBUILD_LIBMAMBA=ON \
      -DBUILD_LIBMAMBAPY=ON \
      -DBUILD_MICROMAMBA=OFF \
      -DBUILD_MAMBA_PACKAGE=OFF \
      -Dlibmamba_ROOT=$PWD/../install"
  python -m build -x --wheel --no-isolation
}

package() {
  cd "$srcdir/$_name"
  cmake --install build/ --prefix "$pkgdir/usr"

  cd "$srcdir/$_name/libmambapy"
  python -m installer --destdir="$pkgdir" dist/*.whl

  install -Dm 644 LICENSE $pkgdir/usr/share/licenses/${pkgname}/LICENSE.txt
}

peippo commented on 2025-06-14 19:41 (UTC)

The version numbers in PKGBUILD and .SRCINFO differ which leads to, e.g., aurutils attempting to re-build micromamba on every run. Could you bump both values to a common version?

brianrobt commented on 2025-06-12 14:35 (UTC)

@bcb, Thanks for catching that! Updated version has been pushed.

bcb commented on 2025-06-11 07:35 (UTC)

I can't build this in a clean chroot (using aurutils) as prepare() tries to use relative paths for the patches. Please replace these with

  patch -p0 -i "${srcdir}/static-off.patch"
  patch -p0 -i "${srcdir}/utils.cpp.patch"

to ensure the patches can be found :).

flying-sheep commented on 2025-06-10 09:47 (UTC)

it does, thank you!

brianrobt commented on 2025-06-09 20:07 (UTC)

@flying-sheep, The latest version should have all of those issues resolved.