Arch Linux User Repository

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

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 :).

it does, thank you!

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

Hi, you don’t actually install libmambapy. building it is ON, but it’s not on my system!

Please fix or stop conflicting with python-libmamba and providing python-libmambapy

❯ paru -Qlq micromamba | treeify 
[/]
 └─usr
    ├─bin
    │  └─mamba
    ├─etc
    │  └─profile.d
    │     └─mamba.sh
    ├─include
    │  └─mamba/**/*.h*
    ├─lib
    │  ├─cmake
    │  │  └─libmamba
    │  │     ├─libmambaConfig.cmake
    │  │     ├─libmambaConfigVersion.cmake
    │  │     ├─libmambaTargets-none.cmake
    │  │     └─libmambaTargets.cmake
    │  ├─libmamba.so
    │  ├─libmamba.so.4
    │  └─libmamba.so.4.0.0
    └─share
       └─licenses
          └─micromamba
             └─LICENSE

That looks like an issue specific to your local environment (i.e., "/home/arthur/.local/bin/ctest").

Micromamba installs without the need for python-cmake in a fresh Docker container: https://github.com/brianrobt/micromamba-aur/blob/master/Dockerfile

[builder@9b949c15df81 ~]$ which ctest
/usr/sbin/ctest
[builder@9b949c15df81 ~]$ ctest --version
ctest version 4.0.2-dirty

CMake suite maintained and supported by Kitware (kitware.com/cmake).

[ 98%] Building CXX object micromamba/CMakeFiles/mamba.dir/src/shell.cpp.o
[ 98%] Building CXX object micromamba/CMakeFiles/mamba.dir/src/umamba.cpp.o
[ 99%] Building CXX object micromamba/CMakeFiles/mamba.dir/src/update.cpp.o
[100%] Building CXX object micromamba/CMakeFiles/mamba.dir/src/version.cpp.o
[100%] Linking CXX executable mamba
[100%] Built target mamba
==> Iniciando check()...
Traceback (most recent call last):
  File "/home/arthur/.local/bin/ctest", line 5, in <module>
    from cmake import ctest
ModuleNotFoundError: No module named 'cmake'
==> ERRO: Uma falha ocorreu em check().
    Abortando...
 -> erro ao construir: micromamba-exit status 4
 -> Falha ao instalar os seguintes pacotes. É necessária a intervenção manual:
micromamba - exit status 4

I had to install python-cmake (python-cmake-bin) to be able to build it.

Just published the new version. Please let us know if there are any issues!

I just got a working patch for the fmt changes which can be seen below. Since I'm not the maintainer of this package, I can't push the changes.

utils.cpp.patch:

--- libmambapy/src/libmambapy/bindings/utils.cpp.orig   2025-05-29 13:26:59.915035009 +0000
+++ libmambapy/src/libmambapy/bindings/utils.cpp    2025-05-29 13:27:33.215447011 +0000
@@ -109,11 +109,11 @@
                         return std::nullopt;
                     }
                     const auto fg = style.get_foreground();
-                    if (fg.is_rgb)
+                    if (!fg.is_terminal_color())
                     {
-                        return { { fmt::rgb(fg.value.rgb_color) } };
+                        return { { fmt::rgb(fg.value()) } };
                     }
-                    return { { static_cast<fmt::terminal_color>(fg.value.term_color) } };
+                    return { { static_cast<fmt::terminal_color>(fg.value()) } };
                 }
             )
             .def_property_readonly(
@@ -125,16 +125,15 @@
                         return std::nullopt;
                     }
                     const auto bg = style.get_background();
-                    if (bg.is_rgb)
+                    if (!bg.is_terminal_color())
                     {
-                        return { { fmt::rgb(bg.value.rgb_color) } };
+                        return { { fmt::rgb(bg.value()) } };
                     }
-                    return { { static_cast<fmt::terminal_color>(bg.value.term_color) } };
+                    return { { static_cast<fmt::terminal_color>(bg.value()) } };
                 }
             )
             .def_property_readonly(
                 "emphasis",
-
                 [](const fmt::text_style& style) -> std::optional<fmt::emphasis>
                 {
                     if (!style.has_emphasis())
@@ -143,7 +142,6 @@
                     }
                     return { style.get_emphasis() };
                 }
-
             )
             .def("__copy__", &copy<fmt::text_style>)
             .def("__deepcopy__", &deepcopy<fmt::text_style>, py::arg("memo"));

Why does it still say provides=(python-libmambapy) then?

Was in a hurry and forgot to remove it.

Can the fmt incompatibility be fixed? The conda package depends on python-libmambapy.

I think so. On the surface it looks like there were only a few breaking API changes limited to a single file. If I have some time today, I'll do a deeper dive and try to get a working patch.

EDIT: Also, once we get this working, I think it's safe to delete the python-libmamba package.