From 4a02cc38ae32b40d8b33137d0f454c952d09f78a Mon Sep 17 00:00:00 2001
From: Julien Jerphanion <git@jjerphan.xyz>
Date: Mon, 26 Aug 2024 22:11:12 +0200
Subject: [PATCH] Reuse `mamba` in the activation script

---
 repo2docker/buildpacks/conda/activate-conda.sh | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/repo2docker/buildpacks/conda/activate-conda.sh b/repo2docker/buildpacks/conda/activate-conda.sh
index 15b771e7..14c46db8 100755
--- a/repo2docker/buildpacks/conda/activate-conda.sh
+++ b/repo2docker/buildpacks/conda/activate-conda.sh
@@ -7,8 +7,8 @@ done
 if [[ "${KERNEL_PYTHON_PREFIX}" != "${NB_PYTHON_PREFIX}" ]]; then
     # if the kernel is a separate env, stack them
     # so both are on PATH, notebook first
-    micromamba activate ${KERNEL_PYTHON_PREFIX}
-    micromamba activate --stack ${NB_PYTHON_PREFIX}
+    mamba activate ${KERNEL_PYTHON_PREFIX}
+    mamba activate --stack ${NB_PYTHON_PREFIX}
 
     # even though it's second on $PATH
     # make sure CONDA_DEFAULT_ENV is the *kernel* env
@@ -17,5 +17,5 @@ if [[ "${KERNEL_PYTHON_PREFIX}" != "${NB_PYTHON_PREFIX}" ]]; then
     # which only contains UI when the two are different
     export CONDA_DEFAULT_ENV="${KERNEL_PYTHON_PREFIX}"
 else
-    micromamba activate ${NB_PYTHON_PREFIX}
+    mamba activate ${NB_PYTHON_PREFIX}
 fi