Mamba not found after running mamba update

[lYlantis]

I installed radioconda from the Windows download link here:

https://github.com/ryanvolz/radioconda?tab=readme-ov-file#download

I was trying to install an OOT module, so I went to install the build dependencies as outlined in this issue

mamba install gnuradio-build-deps

I got the following error: mamba-build-deps.txt

Since I got an error, I thought I would try updating the packages.

mamba update --all

I got the following output: error-log.txt

From there, it looks like the mamba install got messed up:

mamba
'"C:\Users<user>\AppData\Local\radioconda\Library\bin\mamba.exe"' is not recognized as an internal or external command,
operable program or batch file.

Python version: Python 3.12.10 | packaged by conda-forge | (main, Apr 10 2025, 22:08:16) [MSC v.1943 64 bit (AMD64)] on win32

[sfilipkov]

Same issue, was following https://github.com/fventuri/gr-sdrplay3/blob/main/WINDOWS.md

[ryanvolz]

Sorry for the delayed response. Mamba has gone through a version 1 to 2 transition and it hasn't been as painless as it should be. I even opted to keep Mamba v1 in the latest radioconda installer rather than move to v2 because of potential issues like this, but that unfortunately doesn't stop folks from upgrading to v2 manually. So for now I'd say that your best bet is to stick with mamba v1 as installed by the radioconda installer, and avoid upgrading if you can.

As for the dependency error with installing gnuradio-build-deps, there's definitely something broken there. I will investigate.

[ryanvolz]

So the gnuradio-build-deps package was just not installable alongside gnuradio for about the last half a year, due to some conda change that I didn't notice. It should work now. Let me know if you still have issues.

[kgarrels]

Sorry for the delayed response. Mamba has gone through a version 1 to 2 transition and it hasn't been as painless as it should be. I even opted to keep Mamba v1 in the latest radioconda installer rather than move to v2 because of potential issues like this, but that unfortunately doesn't stop folks from upgrading to v2 manually. So for now I'd say that your best bet is to stick with mamba v1 as installed by the radioconda installer, and avoid upgrading if you can.

Any news here?
Can the issue be avoided by pinning mamba to v1?

[srs4511351]

How do we keep from upgrading to mamba v2?
Is it the mamba update --all command?
It is standard practice to have the current packages when building something.