Description of problem:
The base environment is set to be in `/usr`, where conda has no permission to write anything into.
Moreover, it's strange that we have to append `-c base` to every conda command whereas the expected behavior is that the default env is selected automatically.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. conda install argcomplete -c base
NoBaseEnvironmentError: This conda installation has no default base environment. Use
'conda create' to create new environments and 'conda activate' to
argcomplete gets installed
This is pretty much how it is expected to work in Fedora. You can use conda to create and manage new environments, but it doesn't replace dnf for managing the system. Let us know where you think this should be better documented (i.e. where would you have looked?).
Also, I'm not quite sure what you mean about having to add -c base, I get the same error with out it. :)
> Also, I'm not quite sure what you mean about having to add -c base, I get the same error with out it. :)
Oh, that should be -n I think. I just want to switch to the base env.
> i.e. where would you have looked?
Maybe https://developer.fedoraproject.org/tech/languages/python/scipy.html. Or simply in the description of conda (such that dnf info shows it). Or when it prompt to initialize the base env, explain that we should actually create new env instead of using the base env.
I've added a note to the description:
The Fedora conda base environment is special. Unlike a standard
anaconda install base environment it is essentially read-only. You
can only use conda to create and manage new environments.
and while the error message above is a bit strange, it is essentially correct - use conda create to make a new environment.
Thanks! That looks good.