You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Check whether deactivate is a function or executable
type deactivate >/dev/null 2>/dev/null
if [ $? -eq 0 ]; then
. deactivate >/dev/null 2>/dev/null
fi
else
return 0 # nothing to do
fi
fi
The mamba tool has already deprecated/not included the deactivate script so the above checks fail. This results in any pre-activated mamba environments not being deactivated during activation of the conda-pack'd environment. In my own tests this resulted in scripts calling the conda-pack'd activate script to just exit and not run anything after activation.
Conda Info
The tarball was created in CI. You can see the build here:
https://github.com/ssec/sift/actions/runs/5086231711/jobs/9140500154
Conda Config
conda-forge
See https://github.com/ssec/sift/actions/runs/5086231711/jobs/9140500154
Checklist
What happened?
The
bin/deactivate
script created in conda environments is deprecated:https://github.com/conda/conda/blob/9a9610fbaf436b7eef4b13559afb756b1b60d047/conda/shell/bin/deactivate#L3
This file is looked for as part of the activation script of conda-pack:
conda-pack/conda_pack/scripts/posix/activate
Lines 35 to 47 in 08e83ca
The
mamba
tool has already deprecated/not included thedeactivate
script so the above checks fail. This results in any pre-activated mamba environments not being deactivated during activation of the conda-pack'd environment. In my own tests this resulted in scripts calling the conda-pack'dactivate
script to just exit and not run anything after activation.Conda Info
The tarball was created in CI. You can see the build here: https://github.com/ssec/sift/actions/runs/5086231711/jobs/9140500154
Conda Config
Conda list
Additional Context
No response
The text was updated successfully, but these errors were encountered: