-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Node 5 installer on Centos7 tries to use 4.x package during yum install #191
Comments
As a bit more detail, I did originally install version 4.x and it worked, then I ran
Also, it seems to be doing the same thing for the 0.10.x installer. |
I was seeing the same issue. I was able to fix it though...
|
Thanks @neouser99. This fixed my similar problem (node4 installer referencing v5 package.) |
It solved it for me also, many thanks! |
This appears to be solved by cleaning the package manager's cache. Will update the FAQ with this tip which will land in #308 If clearing the cache does not solve your problem, please reopen this issue and we can help debug! |
It solved.Thanks. |
@MaffooBristol absolutely this is a correct & vital part of the solution. I was having difficulty booting the latest CentOS kernal, due to a kernal panic. (I had been going into sudo yum update, yum install, and pip install commands on a previous session that may not all have completed). So I deleted that kernal, while inside the previous kernal version, and went to do But I was getting a bunch of errors then related to nodejs transaction conflicts, upon the yum update command. So how do I get back onto the newest kernal without a kernal panic, and no node transaction conflicts? I tried You have to Finally |
On Debian, if
Add:
Or add the nodejs repo address to your main repo source file directly
Then:
|
In my case (CentOS), I was trying to upgrade from 6.11 to 8.x, and 6.11 was being reinstalled instead, despite cleaning the cache. It turned out I had two .repo files with conflicting versions:
I think this can happen if you run both setup scripts on the same box, and I could confirm it because the
I was able to fix it by removing the offending .repo file, cleaning, and reinstalling:
|
@atavakoli Thanks for the advice, same thing happened to me. |
Add the public key if you get an error from |
For those who are still getting this error of previous version being installed should check whether they have upgraded to later versions (from a previous one) of ubuntu or similar distros which disables third party ppa on upgradation. If yes, then delete |
Using setup_5.x tries to find the package nodejs-4.2.3-1nodesource.el7.centos.x86_64 from the URL https://rpm.nodesource.com/pub_5.x/el/7/x86_64/nodejs-4.2.3-1nodesource.el7.centos.x86_64.rpm, which obviously 404s. Any thoughts? Thanks!
The text was updated successfully, but these errors were encountered: