npm install ghost@0.7.2 fails on Ubuntu 14.04
See original GitHub issueI use Ghost on a server running Ubuntu 14.04, node@v0.10.25, npm@3.5.0.
$ npm install ghost@latest
fails, while $ npm install ghost@0.7.1
works as expected (but with many warnings. I’ve tried installing ghost@latest
with node v4.2.2 using NVM but this did not work either.
Here’s the part of npm-debug.log
that says what is failing:
53996 error Tell the author that this fails on your system:
53996 error npm install semver && node -e "require('./core/server/utils/startup-check.js').nodeVersion()"
If you want the rest of npm-debug.log
, please let me know. I’d be happy to gist it for you.
Issue Analytics
- State:
- Created 8 years ago
- Comments:11 (8 by maintainers)
Top Results From Across the Web
npm install fails on Ubuntu 14.04 with recent node/npm #1212
npm ERR! Failed at the keytar@3.0.0 install script 'node-gyp rebuild'. npm ERR! Make sure you have the latest version of node.js and npm...
Read more >npm install dependencies fails in vagrant ubuntu with shared ...
host OS: Ubuntu 14.04. When doing npm install I get the following errors. npm WARN optional dep failed, continuing imagemin-pngquant@4.0.0 npm WARN optional ......
Read more >How To Install Node.js on an Ubuntu 14.04 Server
In this guide, we'll show you how to get started with Node.js on an Ubuntu 14.04 server. If you are looking to set...
Read more >Running Node-RED locally
Installing with npm. To install Node-RED you can use the npm command that comes with node.js: sudo npm install - ...
Read more >Ubuntu 20.04: ghost install fails
Hello, I'm trying to install Ghost in Ubuntu 20.04 using one of the free Tier ... OS: Ubuntu, v20.04.4 LTS Node Version: v16.15.0...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@kimroen that’s a slight different npm bug to the one that I believe caused the original report here, but we’re tracking that here #6691
For others ending up here, here’s the issue that is tracking the root cause of this issue, as far as I can tell: https://github.com/npm/npm/issues/10379