If ~/.condarc
is a symlink non-default channels do not work
#12956
Labels
good first issue
great for new contributors, code change is envisioned to be trivial/relatively straight-forward
in-progress
issue is actively being worked on
severity::3
major; broken functionality with a workaround
source::community
catch-all for issues filed by community members
type::bug
describes erroneous operation, use severity::* to classify the type
Checklist
What happened?
In my setup, I have several
.condarc.XYZ
files and I used a symlink from.condarc
to one of those based on what I needed. This was done for debugging purposes when I was developing a new conda adapter.I upgraded conda from 23.5.x to 23.7.0 and my non-default channel (conda-forge) disappeared.
This is what
conda info
gave with23.5.x
:This is
conda info
with23.7.0
:Notice that
populated config files
is empty.The content of
~/.condarc
:I tested this on OSX (macbook pro with apple M1) and linux (amd64 debian).
This is not a show stopper for me, I can go back to the regular file for
.condarc
. Thought you may want to know about this. Or, if somebody runs into a the same problem, hopefully they will find this issue.Conda Info
See above for more details...
Conda Config
Conda list
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: