From 0a14433ea8595670f7f288d07898344c656218b6 Mon Sep 17 00:00:00 2001 From: Julien Jerphanion Date: Thu, 22 Aug 2024 17:31:03 +0200 Subject: [PATCH] Use `micromamba activate` instead of `mamba activate` The shell macros are only defined for micromamba but not for mamba. This brings consistency. But then, what was making it working before? Signed-off-by: Julien Jerphanion Co-authored-by: Sylvain Corlay Co-authored-by: Hind Montassif --- 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 14c46db8..15b771e7 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 - mamba activate ${KERNEL_PYTHON_PREFIX} - mamba activate --stack ${NB_PYTHON_PREFIX} + micromamba activate ${KERNEL_PYTHON_PREFIX} + micromamba 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 - mamba activate ${NB_PYTHON_PREFIX} + micromamba activate ${NB_PYTHON_PREFIX} fi