__conda_reactivate not found after a fresh install and an update #700
Comments
|
I've been seeing this too, though i'm not sure where best to report this upstream. cc: @conda-forge/conda @conda-forge/mamba |
|
This has been introduced by conda/conda#14277. |
|
I'm really tempted to backport mamba-org/mamba#3643 2.0.5 was just released with other challenges #697 that you are helping fix (thanks!!!!) but truthfully, it is always good to have a "range" of versions that are installable and usable so one can diagnose problems. e.g. without the ability to downgrade within a range, tools like "git bisect" get REALLY difficult to use since you not only do you need to change your source, but your environment specs. |
The work in mamba-org#3643 was deleted this is really hurting users at conda-forge (myself included) conda-forge/miniforge#700 (comment)
|
Isn't the cost of reverting conda/conda#14277 smaller? |
|
This is for you to decide, but you now have the power to press merge |
|
Let's continue the discussion on mamba-org/mamba#3702. For now, a workaround is to downgrade to |
I was not sure too. But as I install miniforge which integrates both, I thought that it may be a good place. |
|
jjerpan responded ;) and is working to address the issue ;) |
|
This is being fixed by conda. |
|
conda 24.11.2 has been released hours ago; can you let us know if updating conda solves the issue? |
|
Users will need to wait until https://github.com/conda-forge/conda-feedstock is released for conda-forge. |
|
Should be solved once conda-forge/conda-feedstock#248 is merged and its builds are published. |
|
Thanks! It seems merged. I'll close this and work toward a new release. I'm curious if we can go to mamba 2.0.5. I'll try to recreate the other blocker we have. |
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
|
I'm still seeing the error described here when using Is this expected to be fixed yet? Do I need to wait for the |
|
Can you share the version of mamba and conda which you have installed, @nwalters512? |
|
Sure thing: For what it's worth, I also upgraded to conda 24.11.2 and I'm still experiencing the issue. Here's a full reproduction; I was running this in a export arch=`uname -m`
curl -sfLO "https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-Linux-${arch}.sh"
chmod +x "Miniforge3-Linux-${arch}.sh"
./Miniforge3-Linux-${arch}.sh -b
/root/miniforge3/bin/mamba init bash
source /root/.bashrc
mamba --version
# mamba 1.5.11
# conda 24.11.0
# at the very end, this fails with "bash: __conda_reactivate: command not found"
mamba install pygraphviz
# try upgrading conda
conda update conda
# verify new version
mamba --version
# mamba 1.5.11
# conda 24.11.2
# this fails the same way as above
mamba install pygraphviz |
|
Can you update to mamba 1.5.12? |
|
That did not resolve the error. conda install mamba==1.5.12 conda==24.11.2
mamba --version
# mamba 1.5.12
# conda 24.11.2
# This still fails with "bash: __conda_reactivate: command not found"
mamba install pygraphviz |
|
I'm releasing https://github.com/conda-forge/miniforge/releases/tag/24.11.2-0 just now, it will be live in a few hours. Lets close if that can be resolved with that one. There were some growing pains with mamba2 sorry :( |
|
Thanks for releasing that new version! After the upgrade, After several minutes, it starts printing the following line repeatedly, roughly once per second (this is verbatim, I did not accidentally remove any part of the line): I let this run for a few minutes before killing the process; it showed no signs of stopping or doing anything different. I'll add that this is reproducible with other packages as well. Because of this, I'm unfortunately unable to say whether this resolves the initial issue here 😢 This is almost definitely completely unrelated to the problem described by this issue. I'd appreciate any guidance you could offer about where I could file a separate issue about this new problem. |
|
I've unfortunately been hitting this too... conda-forge/conda-feedstock#250 |
|
Ok i've pulled the latest release again. not a good start to the year.... |
|
The problem might come from conda/conda#14455, see: https://github.com/conda/conda/pull/14455/files#r1901556839. cc @kenodegard. |
|
I just hit this as well. fresh install on macOS 15.2 after installing a package with mamba i.e |
|
This will be fixed once conda-forge/conda-feedstock#251 is merged and the associated version of conda and mamba 1.5.12 are used. |
|
let me know if the issue persists |
I'm still pretty unfamiliar with mamba, do I just |
|
please just open a new issue for help. there are stock questions we ask everybody to better help |
|
I can confirm that things are working again with the |
Solution to issue cannot be found in the documentation.
Issue
After a fresh install from https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-Linux-x86_64.sh (corresponding, at this day to version 24.11.0-1), if I do "mamba update --yes --override-channels --channel conda-forge", there is an error "....etc/profile.d/mamba.sh: line 20: __conda_reactivate: command not found".
As said in tickets for mamba it was solved in version 2 of mamba.
But the downloaded script seems to install mamba 1.5.11.
Here is the output of the "mamba update" command:
If I reread configuration files betwwen operations the problem disapeared.
As I did an install from a script which exit at the first non zero exit code (it was 127) I did not see everything.
So I edited my original issue.
Maybe it will disapear when mamba 2 will be directly integrated in Miniforge3.
I have a workarround for my script which now gets the output of the mamba. If output contains "__conda_reactivate" and exit code is 127 it continues.
Installed packages
Environment info
$ base-conda/bin/conda info active environment : None user config file : /home/******/.condarc populated config files : /home/******/base-conda/.condarc /home/******/.condarc conda version : 24.11.1 conda-build version : not installed python version : 3.12.8.final.0 solver : libmamba (default) virtual packages : __archspec=1=skylake __conda=24.11.1=0 __glibc=2.35=0 __linux=6.8.0=0 __unix=0=0 base environment : /home/******/base-conda (writable) conda av data dir : /home/******/base-conda/etc/conda conda av metadata url : None channel URLs : https://conda.anaconda.org/conda-forge/linux-64 https://conda.anaconda.org/conda-forge/noarch package cache : /home/******/base-conda/pkgs /home/******/.conda/pkgs envs directories : /home/******/base-conda/envs /home/******/.conda/envs platform : linux-64 user-agent : conda/24.11.1 requests/2.32.3 CPython/3.12.8 Linux/6.8.0-49-generic ubuntu/22.04.5 glibc/2.35 solver/libmamba conda-libmamba-solver/24.11.1 libmambapy/2.0.5 UID:GID : 1822402247:1822400513 netrc file : /home/******/.netrc offline mode : FalseThe text was updated successfully, but these errors were encountered: