Upgrading from v1.7.x
-
Ran in to an issue during an upgrade. What should I be running to get upgraded? I'm on v1.7.5 according to the Dashboard.
nodebb@clyde:~/nodebb$ git merge origin/v1.10.x Already up to date.
nodebb@clyde:~/nodebb$ git fetch remote: Counting objects: 8548, done. remote: Compressing objects: 100% (7/7), done. remote: Total 8548 (delta 4321), reused 4327 (delta 4321), pack-reused 4220 Receiving objects: 100% (8548/8548), 2.12 MiB | 11.62 MiB/s, done. Resolving deltas: 100% (7066/7066), completed with 1360 local objects. From https://github.com/NodeBB/NodeBB * [new branch] acp-alert-fix -> origin/acp-alert-fix * [new branch] acp-quick-actions -> origin/acp-quick-actions * [new branch] blocks -> origin/blocks * [new branch] chat-kick-support -> origin/chat-kick-support 4d9e2b116..bc18b489e develop -> origin/develop * [new branch] fix-6404 -> origin/fix-6404 * [new branch] hsts-configuration -> origin/hsts-configuration * [new branch] interstitial-fileupload -> origin/interstitial-fileupload 52ab0a00d..3cccbbc1f master -> origin/master + 143fd924d...04d31fe1d patch-pitaj -> origin/patch-pitaj (forced update) * [new branch] renovate/eslint-5.x -> origin/renovate/eslint-5.x * [new branch] renovate/eslint-config-airbnb-base-13.x -> origin/renovate/eslint-config-airbnb-base-13.x * [new branch] renovate/jimp-0.x -> origin/renovate/jimp-0.x * [new branch] renovate/jsdom-11.x -> origin/renovate/jsdom-11.x * [new branch] renovate/mocha-5.x -> origin/renovate/mocha-5.x * [new branch] renovate/mongodb-3.x -> origin/renovate/mongodb-3.x * [new branch] renovate/nyc-12.x -> origin/renovate/nyc-12.x * [new branch] renovate/winston-3.x -> origin/renovate/winston-3.x * [new branch] service-workers -> origin/service-workers * [new branch] spa-authentication -> origin/spa-authentication * [new branch] travis-ci-yarn -> origin/travis-ci-yarn * [new branch] uglify-es -> origin/uglify-es * [new branch] user-blocking -> origin/user-blocking * [new branch] v1.10.x -> origin/v1.10.x * [new branch] v1.8.x -> origin/v1.8.x * [new branch] v1.9.x -> origin/v1.9.x * [new branch] withScores-batch -> origin/withScores-batch * [new branch] yariplus-patch-1 -> origin/yariplus-patch-1 * [new tag] v1.10.1 -> v1.10.1 * [new tag] v1.9.3 -> v1.9.3 * [new tag] v1.10.0 -> v1.10.0 * [new tag] v1.8.0 -> v1.8.0 * [new tag] v1.8.1 -> v1.8.1 * [new tag] v1.9.0 -> v1.9.0 * [new tag] v1.9.1 -> v1.9.1 * [new tag] v1.9.2 -> v1.9.2 nodebb@clyde:~/nodebb$ git checkout v1.10.x Branch 'v1.10.x' set up to track remote branch 'v1.10.x' from 'origin'. Switched to a new branch 'v1.10.x' nodebb@clyde:~/nodebb$ git merge origin/v1.10.x Already up to date. nodebb@clyde:~/nodebb$ git rev-parse --abbrev-ref HEAD v1.10.x nodebb@clyde:~/nodebb$ ./nodebb upgrade Dependencies outdated or not yet installed. Installing them now... /bin/sh: 1: npm: not found Error installing dependencies! message: Command failed: npm install --production stdout: null stderr: null /home/nodebb/nodebb/src/cli/package-install.js:54 throw e; ^ Error: Command failed: npm install --production at checkExecSyncError (child_process.js:601:13) at Object.execSync (child_process.js:641:13) at Object.installAll (/home/nodebb/nodebb/src/cli/package-install.js:45:9) at Object.<anonymous> (/home/nodebb/nodebb/src/cli/index.js:58:18) at Module._compile (module.js:652:30) at Object.Module._extensions..js (module.js:663:10) at Module.load (module.js:565:32) at tryModuleLoad (module.js:505:12) at Function.Module._load (module.js:497:3) at Module.require (module.js:596:17) nodebb@clyde:~/nodebb$
I had taken a snapshot of this VM and was able to revert, so I'm back up and running on v1.7.x
-
Do you not have npm installed? What version of node?
Copyright © 2024 NodeBB | Contributors