Can't create new environments after updating conda #6706
Comments
|
Can you see if fixes your problem? |
|
If that doesn't work, conda should be spitting out an error report if you don't use any |
|
Hi @kalefranz, thanks for the tips. Clean didn't solve the problem. When I take away the -v flags, I just see:
This hangs for a long time. I left it going for about 30 minutes, and it never returned. That's why I added the -v flags to get insight into what is going on. |
|
Can you give me output of |
|
And actually, if you don't mind, share contents of |
|
Just a FYI, |
|
‘conda clean —packages’ doesn’t remove packages that are currently in use, linked into and environment. If you feel like there are packages that should be removed that aren’t we need to address that. If you just want to wipe out the whole package cache altogether, that’s what ‘rm -rf’ is for.
…Sent from my iPhone
On Jan 13, 2018, at 8:36 PM, K.-Michael Aye ***@***.***> wrote:
Just a FYI, conda clean --packages did not work for me in 4.4.7, it kinda pretended to work, but left all stuff in the packages folder, resulting in my hard-drive to getting full. Went back to 4.3 after that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
i can not reproduce my conda clean problems, after upgrading to 4.4.7 straight from 4.3.x. Could it have been caused by something that was repaired between 4.4.0 and .7 ? Because that was my previous upgrade path. |
|
I need the output of when this problem is occurring before I can make any progress on the original issue. |
kalefranz
added
source::community
|
Hi, sorry for the delay. I have been working on other things. I'll try to get you the output of those commands soon. I was doing this work on a virtual machine, which I have since destroyed, so I'll have to reproduce it. |
I guess that's perfect. Because that's exactly what I need to be able to do to understand it and fix it. So you can give me the exact steps now :) |
|
Hi, I noticed that the first error I got was a JSONdecode error: Whic was then followed by the FileNotFound error for every package after that. I looked into it a bit: It seems like it didnt like the old repodata_record.json files that were already there. i kind of hackily fixed this by making it try again after it "fixed" the json file by adding: it took a while to go through every package I had but it worked.. Now this may not be a solution but it might help you to find where the problem is occuring. removing all the packages would probably also fix the problem - I just didnt want to do that because it would take a while to redownload everything again.. |
kalefranz
added
type::bug
|
I am facing the same issue any updates on this. |
|
No idea why, but This is the 2nd time this has happened, and both times I needed to run |
|
@rtruxal: |
|
Hi there, thank you for your contribution to Conda! This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs. If you would like this issue to remain open please:
NOTE: If this issue was closed prematurely, please leave a comment and we will gladly reopen the issue. In case this issue was originally about a project that is covered by the Anaconda issue tracker (e.g. Anaconda, Miniconda, packages built by Anaconda, Inc. like Anaconda Navigator etc), please reopen the issue there again. Thanks! |
|
I had solve this problem through closing my VPN |
|
Hi there, thank you for your contribution! This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs. If you would like this issue to remain open please:
NOTE: If this issue was closed prematurely, please leave a comment. Thanks! |
github-actions
bot
added
the
stale::closed
I just updated conda to v4.4.7, and this seems to break things. In particular, I can't recreate new environments. Here is a snippet of the verbose output after upgrading and trying to create a new environment:
Before the update, everything was working fine.
The text was updated successfully, but these errors were encountered: