-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CondaError: Cannot link a source that does not exist. C:\Users\...\Anaconda3\Scripts\conda.exe #6057
Comments
Do you still get the error after running |
If you need additional help, please include more details. At a minimum, |
Thanks @kalefranz. I had tried |
Had the same error and @AVSuni thank you so much! Also thanks to @kalefranz (it occured when installing spacy) |
…that does not exist'
…that does not exist'
We've run into this with nbconvert as well. I setup a repo to do some testing: On AppVeyor, installing nbconvert from conda-forge has started failing with:
Possibly relevant bits of info:
|
I'm seeing this in damianavila/RISE#315 on win64 / py36 / conda 4.3.22
Reverting to Whereby "fixed" means the broken post-install script didn't run. That was easily fixed with a |
Hi all, I've run into this issue while trying to install the "tweepy" package. [win10 / conda 4.3.30 / Python 3.6.3] Command: Error: CondaError: Cannot link a source that does not exist. C:\Users\Maurice\Anaconda3\Scripts\conda.exe I tried the above steps of |
It's clear to me that this is an issue with entry point creation for python noarch packages on windows. Looking into it. |
That's exactly what's happening.
Sometime around 4.3.8, we removed the embedded As you can see in the above operation plan, conda is unlinked, but then installed last, after pyjwt, which is what needs the entry point binary to hard link. |
Hi I'm kind of new to Python, completely new to Github and I have the same problem as @mccolem19. Was it possible to resolve the problem? Could someone give me a n00b-proof guideline? |
Are there any work-arounds for this? |
You could try:
...until conda is released with the bugfix. |
fix #6057 unlink-link order for python noarch packages on windows 4.4.x
fix #6057 unlink-link order for python noarch packages on windows
Thanks, @henryfbp your solution work for me. |
How can i amend your install command for scrapy as i am also having an issue with installing automats recent version ? |
That I'm not sure of...I don't use Try That command shouldn't install |
I find it strange that you are all Windows users, but it seems that Conda is showing preference to install from the I wonder, would installing the platform-specific build make a difference? For the Automat example (@henryfbp):
|
Cannot link a source that does not exist. D:\Anaconda3\Scripts\conda.exe |
Does |
Tried to run CondaError: Cannot link a source that does not exist. C:\ProgramData\Anaconda3\S |
|
I have more or less the same issue. I'm on Windows 10 using 64-bit python. I need to install Anaconda 5.0 to setup a conda environment with a particular fixed set of package versions for my application. The more recent version (2019.1? 2017.1? I forget) is somehow not compatible and I cannot install that set of versions for some reason, so I had to go back to install the Anaconda 5.0. But then when I go to do "conda install markdown" it fails with this issue.
for reference:
It looks like the conda=4.2.16 does the trick and removes these bizarre dependencies and errors:
It doesn't quite work the same without
|
Thanks. It works. |
|
for those of you who are still stuck on this issue: running |
reverting to 4.2.16 worked for me |
I am trying to install "conda install -c plotly plotly-orca==1.2.1 psutil requests" in anaconda prompt but its not working properly it showed the following problem. ERROR conda.core.link:_execute_actions(337): An error occurred while installing package 'defaults::tqdm-4.46.0-py_0'. CondaError: Cannot link a source that does not exist. D:\Anaconda3\Scripts\conda.exe Attempting to roll back. CondaError: Cannot link a source that does not exist. D:\Anaconda3\Scripts\conda.exe (D:\Anaconda3) C:\Users\Dell\Documents> |
This worked for me. |
this worked for me, thanks |
thanks,this worked for me! |
i can't install jupyter or numpy and always give me this msg |
Per this comment: conda/conda#6057 (comment) According to --help, it will "Remove index cache, lock files, unused cache packages, and tarballs." I don't think this will have an effect since we should be installing into a shiny new VM for CI?
The issue that appears to be happening, where during the update of conda conda.exe is removed and not put back before it's needed by a package (see conda/conda#6057), but I think it's supposed to be solved in a later version of conda? First I need to find out what is installed, hence this change.
The issue that appears to be happening is that during the update of conda conda.exe is removed and not put back before it's needed by a package (see conda/conda#6057). I think it's supposed to be solved in a later version of conda? First I need to find out what is installed, hence this change.
It's possible conda is attempting to install the noarch package version per conda/conda#6057 (comment). So, try deliberately specifying that we want the win64 version installed. Of course this isn't portable to Linux and MacOS when we hopefully add those, but we can deal with special casing later if necessary. Let's just find what the issue is and what works.
It's possible conda is attempting to install the noarch package version per conda/conda#6057 (comment). So, try deliberately specifying that we want the win64 version installed. Of course this isn't portable to Linux and MacOS when we hopefully add those, but we can deal with special casing later if necessary. Let's just find what the issue is and what works.
It's possible conda is attempting to install the noarch package version per conda/conda#6057 (comment). So, try deliberately specifying that we want the win64 version installed. Of course this isn't portable to Linux and MacOS when we hopefully add those, but we can deal with special casing later if necessary. Let's just find what the issue is and what works.
Per this comment: conda/conda#6057 (comment) I'm curious how our current situation might differ from the one in the issue. It appears that the symptoms are the same, but are the causes? So far I've been trying out suggestions based on a little guessing and research, but it's getting to the point where doing a deep dive and really grokking what's happening might be more productive than quickly firing off half thought through fix attempts.
Hi there, thank you for your contribution! This issue has been automatically locked because it has not had recent activity after being closed. Please open a new issue if needed. Thanks! |
I get this error when trying to conda install tqdm. Pip install works fine. However, when trying conda install spacy, I still get the same error because the conda installation for spacy attempts to conda install tqdm.
The text was updated successfully, but these errors were encountered: