fix: Use __conda_activate reactivate instead of __conda_reactivate
#3702
Conversation
The work in mamba-org#3643 was deleted this is really hurting users at conda-forge (myself included) conda-forge/miniforge#700 (comment)
jjerphan
changed the title
__conda_activate reactivate instead of __conda_reactivate
Backport of mamba-org/mamba#3702 Honestly, I've been having alot of trouble with the latest conda version - Conda hanging: conda-forge/conda-feedstock#250 - Can't release conda build 24.11.2 -- conda-forge/miniforge#701 - I think we should just release this small backport in an attempt to help: conda-forge/miniforge#700
…activate` (mamba-org#3702)" This reverts commit ce1d936.
|
Is |
|
i'm not sure. (this is the one line bug that keeps on giving....) |
|
For context, some users reported infinite hanging with micromamba.https://conda.discourse.group/t/staged-recipes-linter-hangs/930 |
|
Should we just delete the micromamba release? |
|
There was a large period of time (nov - Jan 3) where I had lost confidence in conda/mamba because various updates from both kept causing different lockups. On Friday, I pushed conda-forge/conda-feedstock#251 which fixed a bug in a conda warning, so I'm wondering if that might help current users? I don't know anything about micromamba (never tried it) |
The error is resolved and was due to an out-of-date version of staged-recipe apparently. In overall, the activation scripts seem really to be a fragile setup. I am neither confident nor satisfied about it unfortunately… |
|
I'm glad we all get to live to fight an other day! |
The work in #3643 was deleted
this is really hurting users at conda-forge (myself included) conda-forge/miniforge#700 (comment)