Open anthluGH opened 6 years ago
Exactly same problem here with same cause: conda update --all results in: post-link script failed for package defaults::ipykernel-4.8.2-py36_0
any solution yet ?
i too got the same error...
ERROR conda.core.link:_execute(481): An error occurred while installing package 'defaults::ipykernel-4.8.2-py36_0'.
I got the same error. Running conda update ipykernel
, conda clean --all
, then conda update --all
worked for me. You may not need to run the clean command, but I didn't try it without.
@aschey Do you update ipykernel package alone? after that, use conda update --all
to update all packages installed in default environment? or use conda clean --all
to remove all packages cached first and then run conda update --all
?
@anthlu Yes, I ran conda clean --all
before conda update --all
, but I'm not positive that it's necessary. It can't hurt though.
@anthlu I am getting the same behavior for an install of Anaconda from a while back and I have been updating it as I go along (as is expected). I am on Windows 7 - but the error is the same. I get the same error on my Windows 10 machine with the same build on it (tested after I ran into this issue). I do get some strange text at the command line after I run the original conda update conda
to update to 4.4.11.
My Windows 7 conda info
shows the following:
(base) C:\Windows\system32>conda info
active environment : base
active env location : C:\Users\nfsdp\AppData\Local\Continuum\Anaconda3
shell level : 1
user config file : C:\Users\nfsdp\.condarc
populated config files : C:\Users\nfsdp\.condarc
conda version : 4.4.11
conda-build version : not installed
python version : 3.6.4.final.0
base environment : C:\Users\nfsdp\AppData\Local\Continuum\Anaconda3 (writable)
channel URLs : https://conda.anaconda.org/anaconda-fusion/win-64
https://conda.anaconda.org/anaconda-fusion/noarch
https://repo.continuum.io/pkgs/main/win-64
https://repo.continuum.io/pkgs/main/noarch
https://repo.continuum.io/pkgs/free/win-64
https://repo.continuum.io/pkgs/free/noarch
https://repo.continuum.io/pkgs/r/win-64
https://repo.continuum.io/pkgs/r/noarch
https://repo.continuum.io/pkgs/pro/win-64
https://repo.continuum.io/pkgs/pro/noarch
https://repo.continuum.io/pkgs/msys2/win-64
https://repo.continuum.io/pkgs/msys2/noarch
package cache : C:\Users\nfsdp\AppData\Local\Continuum\Anaconda3\pkgs
C:\Users\nfsdp\AppData\Local\conda\conda\pkgs
envs directories : C:\Users\nfsdp\AppData\Local\Continuum\Anaconda3\envs
C:\Users\nfsdp\AppData\Local\conda\conda\envs
C:\Users\nfsdp\.conda\envs
platform : win-64
user-agent : conda/4.4.11 requests/2.18.4 CPython/3.6.4 Windows/7 Windows/6.1.7601
administrator : True
netrc file : None
offline mode : False
I re-installed conda 4.4.10 and then re-updated to 4.4.11 and reproduced the error text at the bottom of the code block below:
(base) C:\Windows\system32>conda update conda
Solving environment: ...working... done
## Package Plan ##
environment location: C:\Users\nfsdp\AppData\Local\Continuum\Anaconda3
added / updated specs:
- conda
The following packages will be UPDATED:
conda: 4.4.10-py36_0 --> 4.4.11-py36_0
Proceed ([y]/n)?
Preparing transaction: ...working... done
Verifying transaction: ...working... done
Executing transaction: ...working... done
(base) C:\Users\nfsdp>block should really be the equivalent of
'block' is not recognized as an internal or external command,
operable program or batch file.
I have no idea what this information on "block" is referring to. But conda 4.4.11 is installed per conda info
.
@AcmeNuclear I also meet the problem you mentioned. When I update the conda package after installing the anaconda, it also prints the information like "block should really be the equivalent of". So I think the problem may be caused by the package itself.
same issue observed on Win10.
same issue, conda update ipykernel and then conda update --all worked for me (Win10 Ent. 1607)
I had the same issue as well. Ran conda update ipykernel
and then conda update --all
and everything updated fine. Looks like the clean isn't needed. EDIT: I take it all back. When running spyder I get an internal error and it cannot connect to the kernel, I had to reinstall anaconda to fix this as running conda install --version 0
returned a similar error to the one above.
When trying to do conda update ipykernel
from a fresh installation of anaconda 5.1.0 it wants to replace anaconda 5.1.0-py36_2 --> custom-py36h363777c_0
which is kind of fishy.
which is kind of fishy.
This is the intended behaviour. As soon as any version changes to be different from the one in the installer the anaconda metapackage version changes to custom to reflect this.
Sure I understand that this change of version number is neccessary if the version indeed changes. What I don't like is, that an update needs a special (not knonw by number) version in the first place.
Maybe I did not look carefully enough in the past, but I don't think this happend in the past, when I did a conda update --all
, which I also did after the mentioned conda update ipykernel
. But now the anaconda version remains custom
The anaconda package is a metapackage that is released with each release of the AD installers. It specifies exactly all of the version numbers for all of the packages in the installer. Its own version number corresponds to the AD release number.
So once any package is updated such that no existing anaconda metapackage shares that exact set of version numbers we change it to custom to indicate that you no longer have a set of packages that match any release.
Is that clear?
Ok, thanks for making this clear.
Same issue on Windows Server 2012 R2. The solution proposed by @aschey seems to do the trick for now.
@mingwandroid - Ray, given what you say up above, what is the best path forward. I still have the issue that when I do a standard update that it fails when it typically works. I will be the first to admit that I did not follow everything above regarding the Andaconda package installer versioning (vs. I suspect just updating through Conda?). Is there a more reliable method to keeping my packages up to date other than what I have been doing? I switched to using command line Conda when the Anaconda Navigator update function kept failing on me (I ran update but they would not take for some reason. Thanks!!
conda update --all
is the canonical way to update all of your packages (note due to version constrains it may not be possible to update everything to the latest but conda
will do its best to update as many as possible).
Our team has been considering renaming the anaconda
metapackage to something like anaconda-release
or anaconda-pinned
and then removing the exact versions pins from a new anaconda
metapackage. The idea is to lessen the surprise that people encounter here when they believe that issuing conda update anaconda
means that conda will do its best to update all their installed packages (or to be more precise, those packages installed when they ran the Anaconda Distribution installer) to the latest available ones when it does not.
I did not follow everything above regarding the Andaconda package installer versioning
If there are some specific parts of what I wrote that I could explain better then please let me know.
Have exactly the same issue (same error) on Windows 10. After reading the above, ran "conda update ipykernel" - it ran successfully. Then I ran "conda update --all" again. It seems to be working for me.
@dl7631 this worked for me as well! I tried the conda clean --all, and conda update --all, failed. But firs updating the ipykernel did work, and after that conda update --all. Thanks!
FYI - I followed the sequence as listed above conda update ipykernel
, conda clean --all
, and finally conda update --all
. This appears to have worked. When I opened Spyder the first time it did give some error / warning issues with connecting to the kernel, but those flashed by and it resolved itself and ran fine after that. Thanks to all for the help - much appreciated.
I am Win10 amd64 trying to install xgboost and I get this error when updating the packages: my version of python is 3.6.3 conda install -c anaconda py-xgboost
An error occurred while uninstalling package 'defaults::qt-5.6.2-vc14h6f8c307_12'. PermissionError(13, 'Access is denied')..
The solution for me was run anaconda as adminstrator.
windows10 Pro, however, when I tried conda update ipykernel, apppearing conda: 4.5.4-py36_0 --> 4.3.30 , many packages went to the lower versions. Thanks!
same issue observed on Win10 1803
I also encountered the 'block should really be the equivalent of' automatic entry error after updating. I am new to Python and learning to use lmfit, executed the command as instructed, then updated as Anaconda instructed. Reading comments here, I then checked to see if the update was successful as AcmeNuclear did.
Here is the text from my Anaconda Prompt (with username replaced for anonymity):
(base) C:\Users\UserName>conda install -c GSECARS lmfit
Solving environment: done
==> WARNING: A newer version of conda exists. <==
current version: 4.4.10
latest version: 4.5.4
Please update conda by running
$ conda update -n base conda
## Package Plan ##
environment location: C:\Users\UserName\Anaconda3
added / updated specs:
- lmfit
The following packages will be downloaded:
package | build
---------------------------|-----------------
lmfit-0.9.10 | py36_0 188 KB GSECARS
uncertainties-3.0.2 | py36_0 118 KB GSECARS
asteval-0.9.12 | py36_0 43 KB GSECARS
------------------------------------------------------------
Total: 349 KB
The following NEW packages will be INSTALLED:
asteval: 0.9.12-py36_0 GSECARS
lmfit: 0.9.10-py36_0 GSECARS
uncertainties: 3.0.2-py36_0 GSECARS
Proceed ([y]/n)? y
Downloading and Extracting Packages
lmfit 0.9.10: ################################################################################################# | 100%
uncertainties 3.0.2: ########################################################################################## | 100%
asteval 0.9.12: ############################################################################################### | 100%
Preparing transaction: done
Verifying transaction: done
Executing transaction: done
(base) C:\Users\UserName>conda update -n base conda
Solving environment: done
## Package Plan ##
environment location: C:\Users\UserName\Anaconda3
added / updated specs:
- conda
The following packages will be downloaded:
package | build
---------------------------|-----------------
conda-4.5.4 | py36_0 1.0 MB
The following packages will be UPDATED:
conda: 4.4.10-py36_0 --> 4.5.4-py36_0
Proceed ([y]/n)? y
Downloading and Extracting Packages
conda 4.5.4: ################################################################################################## | 100%
Preparing transaction: done
Verifying transaction: done
Executing transaction: done
(base) C:\Users\UserName>block should really be the equivalent of
'block' is not recognized as an internal or external command,
operable program or batch file.
(base) C:\Users\UserName>conda info
active environment : base
active env location : C:\Users\UserName\Anaconda3
shell level : 1
user config file : C:\Users\UserName\.condarc
populated config files : C:\Users\UserName\.condarc
conda version : 4.5.4
conda-build version : 3.4.1
python version : 3.6.4.final.0
base environment : C:\Users\UserName\Anaconda3 (writable)
channel URLs : https://repo.anaconda.com/pkgs/main/win-64
https://repo.anaconda.com/pkgs/main/noarch
https://repo.anaconda.com/pkgs/free/win-64
https://repo.anaconda.com/pkgs/free/noarch
https://repo.anaconda.com/pkgs/r/win-64
https://repo.anaconda.com/pkgs/r/noarch
https://repo.anaconda.com/pkgs/pro/win-64
https://repo.anaconda.com/pkgs/pro/noarch
https://repo.anaconda.com/pkgs/msys2/win-64
https://repo.anaconda.com/pkgs/msys2/noarch
package cache : C:\Users\UserName\Anaconda3\pkgs
C:\Users\UserName\AppData\Local\conda\conda\pkgs
envs directories : C:\Users\UserName\Anaconda3\envs
C:\Users\UserName\AppData\Local\conda\conda\envs
C:\Users\UserName\.conda\envs
platform : win-64
user-agent : conda/4.5.4 requests/2.18.4 CPython/3.6.4 Windows/10 Windows/10.0.16299
administrator : False
netrc file : None
offline mode : False
Just don't forget to run Anaconda prompt as Administrator... That was my problem.
@psy-therapist thanks this is also my problem
Same problem, couldn't conda update conda from non-admin user account on Windows 10. I kept getting "ERROR conda.core.link:_execute(502): An error occurred while uninstalling package" Tried conda update ipykernel from same user account - same problem. Closed Anaconda Prompt and re-opened as Administrator Ran "conda update ipykernel" which worked this time and also updated conda to 4.5.9 closed Anaconda Prompt and reopened NOT as Administrator "conda update conda" worked this time and it also updated openssl-1.0.2o and conda-4.5.9 Interesting that it updated conda again ????
I think i have tried everything is this thread with no luck, open to suggestions...
Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic
MSI:~$ conda update --all Solving environment: done
environment location: ... pyparsing-2.2.0 | 96 KB | ####################################### | 100% anaconda-client-1.7. | 136 KB | ####################################### | 100% incremental-17.5.0 | 25 KB | ####################################### | 100% Preparing transaction: done Verifying transaction: done Executing transaction: failed ERROR conda.core.link:_execute(502): An error occurred while uninstalling package 'defaults::anaconda-5.2.0-py36_3'. PermissionError(13, 'Permission denied') Attempting to roll back.
Rolling back transaction: done
PermissionError(13, 'Permission denied')
Preparing transaction: done Verifying transaction: done Executing transaction: failed ERROR conda.core.link:_execute(502): An error occurred while uninstalling package 'defaults::anaconda-5.2.0-py36_3'. PermissionError(13, 'Access is denied') Attempting to roll back.
Rolling back transaction: done
PermissionError(13, 'Access is denied')
i think in have no choice! uninstall anaconda.... (2 months of work!!) reinstall back and do the necessary library....
can i change Linux based OS to install anaconda for stable run.... To avoid wasting time!
any advice please
2 months of work!!
It is not advisable to store your work in the anaconda folder.
On Wed, Aug 22, 2018, 4:54 AM JDeepAI notifications@github.com wrote:
i think in have no choice! uninstall anaconda.... (2 months of work!!) reinstall back and do the necessary library....
can i change Linux based OS to install anaconda for stable run.... To avoid wasting time!
any advice please
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ContinuumIO/anaconda-issues/issues/8733#issuecomment-414901915, or mute the thread https://github.com/notifications/unsubscribe-auth/AA_pdNSPf3okfff2yTYaPqjFYqZrF4JSks5uTNYEgaJpZM4SavPb .
Using Win10 fall update insiders edition 12/23/2018. All the above suggestions failed for me. Had to go back to Anaconda 4.4.1 [was getting http error 'cannot connect' etc. and could not update] Now seems to be working [BTW I installed/uninstalled various versions of Anaconda a dozen times or more]
Just don't forget to run Anaconda prompt as Administrator... That was my problem.
The same as me:) but really struggled for a long time before doing right
In general people should avoid installing our software as administrator. We design our stuff to work without needing to do that. If you have installed for All Users
then you must continue to use administrator, still, for most people there's little reason to do that. Use a normal user install and you will not need to worry (or risk breaking your computer).
Hi Ray, Thank you for explaining to me. I probably chose 'All Users' when I installed:(
Ray Donnelly notifications@github.com 于2019年6月4日周二 下午2:20写道:
In general people should avoid installing our software as administrator. We design our stuff to work without needing to do that. If you have installed for All Users then you must continue to use administrator, still, for most people there's little reason to do that. Use a normal user install and you will not need to worry (or risk breaking your computer).
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ContinuumIO/anaconda-issues/issues/8733?email_source=notifications&email_token=AMH7TYF6R5KI2JE6YNVD2RLPY2W47A5CNFSM4ETK6PN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW5N2FQ#issuecomment-498785558, or mute the thread https://github.com/notifications/unsubscribe-auth/AMH7TYC33XVNZKAYHAO7ER3PY2W47ANCNFSM4ETK6PNQ .
Actual Behavior
I downloaded and installed the latest Anaconda3-5.1.0-Windows-x86_64, and I try to update all packages after installing the product. I run the command "conda update --all" with Administrator privilege, it checked and downloaded the packages required, but when installing those packages, the conda shows failed ERROR conda.core.link:_execute(481): An error occurred while installing package 'defaults::ipykernel-4.8.2-py36_0'. LinkError: post-link script failed for package defaults::ipykernel-4.8.2-py36_0 running your command again with
-v
will provide additional information location of failed script: C:\ProgramData\Anaconda3\Scripts.ipykernel-post-link.bat ==> script messages <==