How to Upgrade from v1.13.3 to v1.14.0?
-
**I tried to follow upgrade doc.
it is getting an errors.please guide me.
currently hosted in heroku. i cloned that into my local pc.
then what should i do?**freesv@varun-deva:~/buforum$ git fetch freesv@varun-deva:~/buforum$ git reset --hard origin/v1.14.0 fatal: ambiguous argument 'origin/v1.14.0': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' freesv@varun-deva:~/buforum$ git reset --hard origin/v1.14.x fatal: ambiguous argument 'origin/v1.14.x': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' freesv@varun-deva:~/buforum$ git checkout v1.14.x error: pathspec 'v1.14.x' did not match any file(s) known to git freesv@varun-deva:~/buforum$ git checkout v1.12.x error: pathspec 'v1.12.x' did not match any file(s) known to git freesv@varun-deva:~/buforum$ ./nodebb upgrade Dependencies outdated or not yet installed. Installing them now... npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3. npm WARN deprecated bson@1.0.9: Fixed a critical issue with BSON serialization documented in CVE-2019-2391, see https://bit.ly/2KcpXdo for more details npm ERR! Unexpected end of JSON input while parsing near '...vSYVuf9vaftnyO0\nVAo7' npm ERR! A complete log of this run can be found in: npm ERR! /home/freesv/.npm/_logs/2020-07-04T07_29_58_093Z-debug.log Error installing dependencies! message: Command failed: npm install --production stdout: null stderr: null /home/freesv/buforum/src/cli/package-install.js:72 throw e; ^ Error: Command failed: npm install --production at checkExecSyncError (child_process.js:629:11) at Object.execSync (child_process.js:666:13) at Object.installAll (/home/freesv/buforum/src/cli/package-install.js:63:9) at Object.<anonymous> (/home/freesv/buforum/src/cli/index.js:60:18) at Module._compile (internal/modules/cjs/loader.js:778:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Module.require (internal/modules/cjs/loader.js:692:17) freesv@varun-deva:~/buforum$ git fetch freesv@varun-deva:~/buforum$ git checkout v1.14.x error: pathspec 'v1.14.x' did not match any file(s) known to git freesv@varun-deva:~/buforum$ git checkout v1.14.0 error: pathspec 'v1.14.0' did not match any file(s) known to git freesv@varun-deva:~/buforum$ git merge origin/v1.14.x merge: origin/v1.14.x - not something we can merge freesv@varun-deva:~/buforum$ git checkout v1.x.x error: pathspec 'v1.x.x' did not match any file(s) known to git freesv@varun-deva:~/buforum$ git pull && ./nodebb upgrade Already up to date. Dependencies outdated or not yet installed. Installing them now... npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3. npm WARN deprecated bson@1.0.9: Fixed a critical issue with BSON serialization documented in CVE-2019-2391, see https://bit.ly/2KcpXdo for more details npm ERR! Unexpected end of JSON input while parsing near '...vSYVuf9vaftnyO0\nVAo7' npm ERR! A complete log of this run can be found in: npm ERR! /home/freesv/.npm/_logs/2020-07-04T07_32_48_769Z-debug.log Error installing dependencies! message: Command failed: npm install --production stdout: null stderr: null /home/freesv/buforum/src/cli/package-install.js:72 throw e; ^ Error: Command failed: npm install --production at checkExecSyncError (child_process.js:629:11) at Object.execSync (child_process.js:666:13) at Object.installAll (/home/freesv/buforum/src/cli/package-install.js:63:9) at Object.<anonymous> (/home/freesv/buforum/src/cli/index.js:60:18) at Module._compile (internal/modules/cjs/loader.js:778:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) at Module.load (internal/modules/cjs/loader.js:653:32) at tryModuleLoad (internal/modules/cjs/loader.js:593:12) at Function.Module._load (internal/modules/cjs/loader.js:585:3) at Module.require (internal/modules/cjs/loader.js:692:17) freesv@varun-deva:~/buforum$ npm install --production npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3. npm WARN deprecated bson@1.0.9: Fixed a critical issue with BSON serialization documented in CVE-2019-2391, see https://bit.ly/2KcpXdo for more details npm ERR! Unexpected end of JSON input while parsing near '...vSYVuf9vaftnyO0\nVAo7' npm ERR! A complete log of this run can be found in: npm ERR! /home/freesv/.npm/_logs/2020-07-04T07_34_36_030Z-debug.log freesv@varun-deva:~/buforum$
-
Getting Like This. Why??
@administratorsfreesv@varun-deva:~/buforum$ git checkout v1.14.0 error: pathspec 'v1.14.0' did not match any file(s) known to git freesv@varun-deva:~/buforum$
-
@Varun-Ganesh-D said in How to Upgrade from v1.13.3 to v1.14.0?:
Getting Like This. Why??
@administratorsfreesv@varun-deva:~/buforum$ git checkout v1.14.0 error: pathspec 'v1.14.0' did not match any file(s) known to git freesv@varun-deva:~/buforum$
You didn't include it here. I'm guessing that you forgot to git fetch, which is what makes that possible.
-
@scottalanmiller said in How to Upgrade from v1.13.3 to v1.14.0?:
fetch
No, I Executed that command
See it.
I Cloned Heroku Repo to My Laptop.If I Execute the Same Command in Heroku Bash It Showing Different Error
-
@Varun-Ganesh-D said in How to Upgrade from v1.13.3 to v1.14.0?:
I Cloned Heroku Repo to My Laptop.
Oh, I don't know anything about the Heroku repos. I just use the NodeBB ones.
-
@scottalanmiller yes.
But whats that problem when i clone to local system and run -
@Varun-Ganesh-D said in How to Upgrade from v1.13.3 to v1.14.0?:
If I Execute the Same Command in Heroku Bash It Showing Different Error
That makes it look like you aren't in a git folder at all, at least that's the error.
-
@Varun-Ganesh-D said in How to Upgrade from v1.13.3 to v1.14.0?:
@scottalanmiller yes.
But whats that problem when i clone to local system and runWhat did you clone? I'm not aware of any Heroku repo.
-
Try this command, let's see what it says..
git branch -r
This will list what branches are available to you.
-
@scottalanmiller That's Ok.
Is it possible to upgrade by downloading latest version and install? while installing what happens if i give same database credentials?
i think its not proper way to upgrade. -
@Varun-Ganesh-D said in How to Upgrade from v1.13.3 to v1.14.0?:
@scottalanmiller That's Ok.
Is it possible to upgrade by downloading latest version and install? while installing what happens if i give same database credentials?
i think its not proper way to upgrade.That's not the proper way and risks the database not being brought up through the versions correctly. But if you can download, you should be able to get from git, since the two pull from the same place.
-
Do this command...
git config -l
That should show where you've set the git to pull from.
-
@scottalanmiller Yea
Problem is there in Git.
Since ive used heroku it configured with its Git Instead of NodeBB Git.
Let Me try to re configure thatBut Fresh Downloaded NodeBB.zip has no .git folder.
Waiting for Some peoples reply who hosted under Heroku
they may know how to upgrade -
@Varun-Ganesh-D said in How to Upgrade from v1.13.3 to v1.14.0?:
But Fresh Downloaded NodeBB.zip has no .git folder.
Right, don't do that. Use git, but pull from NodeBB, not Heroku. Don't use alternative sources, and don't use ZIP files. Just stick to the standard and it should be fine.
-
@Varun-Ganesh-D said in How to Upgrade from v1.13.3 to v1.14.0?:
Waiting for Some peoples reply who hosted under Heroku
they may know how to upgradeI've not use Heroku in forever and never with NodeBB, but Heroku has to give you access to any GIT repo that you want. So nothing on Heroku should require something special. Just install on Heroku the same as you would install anywhere. The issue, I think, is attempting to do something special for Heroku instead of following the standard NodeBB procedures.
-
@scottalanmiller Btw how to change git remote URL
-
@Varun-Ganesh-D said in How to Upgrade from v1.13.3 to v1.14.0?:
Btw how to change git remote URL
origin doesn't exist yet, so you can't change it, but only add it, like this...
git remote add origin URL
-
@scottalanmiller ok
After adding origin it clones or pulls update from origin??