Closed danielsf closed 8 years ago
Did you have a hand-modified ~/.condarc
? I've seen similar errors when I'd modify it by hand and introduce mistakes.
Could you check if this is reproducible?
I have never touched my .condarc
I have already experienced this problem both on my laptop and on lsst-dev. Is there another test you would like me to perform?
Can you give me steps to reproduce it? I'm failing miserably right now :(.
it really is just
conda config --add channels http://eupsforge.net/conda/dev
my PATH is
/home/danielsf/conda-lsst/bin/:/home/danielsf/conda-lsst/miniconda/bin/:/opt/rh/devtoolset-3/root/usr/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/danielsf/bin
which conda
is
~/conda-lsst/miniconda/bin/conda
and my .condarc is
channels:
For what it's worth, if I first remove the dev channel and then try to add it again, I also get the error.
[ewok:~/lsstRepos/conda-lsst/miniconda] lynnej% conda config --remove channels http://eupsforge.net/conda/dev --force [ewok:~/lsstRepos/conda-lsst/miniconda] lynnej% more ~/.condarc channels:
However, if I then completely remove the ~/.condarc file and try to add it the channel, it works. [ewok:~/lsstRepos/conda-lsst/miniconda] lynnej% rm ~/.condarc remove /Users/lynnej/.condarc? y [ewok:~/lsstRepos/conda-lsst/miniconda] lynnej% conda config --add channels http://eupsforge.net/conda/dev [ewok:~/lsstRepos/conda-lsst/miniconda] lynnej%
-Lynne
On Thu, Jan 14, 2016 at 1:13 PM danielsf notifications@github.com wrote:
it really is just
conda config --add channels http://eupsforge.net/conda/dev
my PATH is
which conda
is
``` ~/conda-lsst/miniconda/bin/conda
and my
.condarc
ischannels:
- http://eupsforge.net/conda/dev_testing
defaults
— Reply to this email directly or view it on GitHub https://github.com/mjuric/conda-lsst/issues/40#issuecomment-171781351.
True: I also did not start seeing this error until I tried removing a channel with conda config --remove
I think the 'remove' feature must be buggy. The fact that you have to use --force in order to use it might be an indication.
On Thu, Jan 14, 2016 at 1:58 PM danielsf notifications@github.com wrote:
True: I also did not start seeing this error until I tried removing a channel with conda config --remove
— Reply to this email directly or view it on GitHub https://github.com/mjuric/conda-lsst/issues/40#issuecomment-171794381.
This is beginning to sound familiar -- I think @cwwalter encountered this as well (and we traced it to a bug in conda config --remove
, and then I forgot about it). I'll open an issue with upstream.
Yes, that's correct. I had to manually remove the file.
Issue opened upstream: https://github.com/conda/conda/issues/2013
In the meantime, don't use conda --remove
to manipulate ~/.condarc
; edit it by hand, if needed.
Just running
conda config --add channels http://eupsforge.net/conda/dev
givesError: Could not parse the yaml file. Use -f to use the yaml parser (this will remove any structure or comments from the existing .condarc file). Reason: couldn't parse modified yaml
This can be avoided with
conda config --force --add channels http://eupsforge.net/conda/dev
, but the behavior seems odd.