NodeBB stuck at v0.7.0 - Says no update is found



  • I was about to update the nodebb-theme-persona when I recieved the message that my NodeBB was not up-to-date for the newest version of Persona, but when going on the dashboard it says i am up-to-date.

    I tried running the ./nodebb upgrade but that did not find any update either.


  • Admin

    ... try again 😉

    But keep in mind you have to git pull before you run ./nodebb upgrade.



  • @julian
    After doing "git pull" and recieving the "Already up-to-date" message i ran the ./notebb upgrade and recieved this error.

    module.js:340
    throw err;
    ^
    Error: Cannot find module 'colors'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/root/nodebb/nodebb:3:14)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)


  • Admin

    Please refer to the Upgrade Documentation 😄

    Hopefully all of your questions will be answered there.



  • @julian
    I think i made a mistake on the way, when trying to run a command as simple as ./nodebb stop
    I receive the same error.

    module.js:340
    throw err;
    ^
    Error: Cannot find module 'colors'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/root/nodebb/nodebb:3:14)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)


  • GNU/Linux

    @julian what would explain a git pull , and then ./nodebb upgrade

    start server and it says still 0.7.0 nothing changed 😘


  • Admin

    @MySelfLuls Run npm i first, and then try to stop your NodeBB again.



  • @julian
    Just tried running npm i.

    Recieved this error.
    I honestly suspect I have corrupted the system.

    npm ERR! install Couldn't read dependencies
    npm ERR! Failed to parse json
    npm ERR! Unexpected token <
    npm ERR! File: /root/nodebb/package.json
    npm ERR! Failed to parse package.json data.
    npm ERR! package.json must be actual JSON, not just JavaScript.
    npm ERR!
    npm ERR! This is not a bug in npm.
    npm ERR! Tell the package author to fix their package.json file. JSON.parse

    npm ERR! System Linux 3.16.0-28-generic
    npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "i"
    npm ERR! cwd /root/nodebb
    npm ERR! node -v v0.10.25
    npm ERR! npm -v 1.4.21
    npm ERR! file /root/nodebb/package.json
    npm ERR! code EJSONPARSE
    npm ERR!
    npm ERR! Additional logging details can be found in:
    npm ERR! /root/nodebb/npm-debug.log
    npm ERR! not ok code 0


  • Admin

    @MySelfLuls

    $ git checkout v0.7.x
    $ git reset --hard HEAD origin/v0.7.x
    $ npm i
    $ ./nodebb upgrade
    


  • @julian

    When using the git checkout v0.7.x i recieved this error

    Already on 'v0.7.x'
    Your branch is ahead of 'origin/v0.7.x' by 12 commits.
    (use "git push" to publish your local commits)

    I was unsure if it was an actual error and went ahead to the git reset --hard HEAD origin/v0.7.x

    Then I recieved this error:

    fatal: Cannot do hard reset with paths.



  • Seems like we're both on the same boat @MySelfLuls

    This is indeed very strange.

    My post here

    Edit: It seems they have pulled v0.7.1 for now


  • Admin

    Hey guys, let's stick to one post for convenience's sake 😄


  • Admin

    Please refer to the latest instructions here: https://community.nodebb.org/topic/6088/update-merge-issue/7


Locked
 

Suggested Topics

| |