Update, merge issue..

General Discussion
  • @MySelfLuls Cerulean is quite out of date, I wouldn't recommend installing it.

    npm unlink nodebb-plugin-cerulean

    Then try again.

  • @julian
    Thanks a lot.
    Btw.
    What was added in the newest update?

  • @julian Followed latest instructions in this post, got this.

    Error: Cannot find module './styles'
    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> (/home/errapolis/nodebb/node_modules/colors/lib/colors.js:36:34)
    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 Module.require (module.js:364:17)
    
  • Seems like the colors module wasn't installed properly... try reinstalling it? npm i colors

  • I knew i'd encountered a problem like that before, that worked, though subsequently I ran upgrade then it was the same issue with "cookie", then upgrade, then "crc", now "debug". Is there a quicker way to find all those needed if more follow?

  • @julian would this bunch be causing the problem now that the dependency requirements are more strict?

    unmet.JPG

    If so, any hints? Stuck on this:

    Capture.JPG

  • @Danny-McWilliams Nope, that should only apply to bundled plugins (mentions, vanilla/lavender/persona theme, markdown, etc).

    If you're getting more of those "cannot find module" errors, then perhaps your dependencies were not completely installed.

    Please run npm install.

  • Ok @julian just did - same result, sadly. unmet dependency list then the same as the second picture.

    Tried to start nodebb, this was in log.

    Capture.JPG

  • @julian i run ./nodebb upgrade after it looks successful npm i command ?

    ./nodebb upgrade
    
    module.js:340
        throw err;
              ^
    Error: Cannot find module 'ini'
        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/node_modules/npm/node_modules/config-chain/index.js:4:11)
        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 Module.require (module.js:364:17)
    
    21/7 20:21 [25890] - error: Error: Cannot find module './build/Release/magic'
        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/node_modules/mmmagic/index.js:3:13)
        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 Module.require (module.js:364:17)
    Error: Cannot find module './build/Release/magic'
        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/node_modules/mmmagic/index.js:3:13)
        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 Module.require (module.js:364:17)
    
    module.js:340
        throw err;
        ^
    Error: Cannot find module './build/Release/magic'
        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/node_modules/mmmagic/index.js:3:13)
        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 Module.require (module.js:364:17)
    
  • npm i is your phriend

    NodeBB Upgrade Complete!

  • @Danny-McWilliams said:

    Ok @julian just did - same result, sadly. unmet dependency list then the same as the second picture.

    Tried to start nodebb, this was in log.

    Capture.JPG

    Usually when I get issues like this, I have to do an npm cache clean and then an npm install or npm rebuild

  • for some reason my ./nodebb upgrade script after git pull missed a ton of modules

  • trying to update, but npm i shows me that

    npm WARN unmet dependency /home/leksar/nodebb/node_modules/nodebb-plugin-shoutbox requires async@'~0.2.9' but will load
    npm WARN unmet dependency /home/leksar/nodebb/node_modules/async,
    npm WARN unmet dependency which is version 0.9.2
    npm WARN unmet dependency /home/leksar/nodebb/node_modules/nodebb-plugin-shoutbox requires string@'~1.8.0' but will load
    npm WARN unmet dependency /home/leksar/nodebb/node_modules/string,
    npm WARN unmet dependency which is version 3.3.0
    npm ERR! peerinvalid The package nodebb-theme-vanilla does not satisfy its siblings' peerDependencies requirements!
    npm ERR! peerinvalid Peer [email protected] wants nodebb-theme-vanilla@>=0.0.137
    npm ERR! peerinvalid Peer [email protected] wants nodebb-theme-vanilla@~0.0.18
    
    npm ERR! System Linux 3.16.0-43-generic
    npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "i"
    npm ERR! cwd /home/leksar/nodebb
    npm ERR! node -v v0.10.25
    npm ERR! npm -v 1.3.10
    npm ERR! code EPEERINVALID
    npm ERR!
    npm ERR! Additional logging details can be found in:
    npm ERR!     /home/leksar/nodebb/npm-debug.log
    npm ERR! not ok code 0
    

    Tried to do npm unlink nodebb-plugin-spam-be-gone and npm unlink nodebb-theme-ifsta-ui, but the result is the same. Any ideas ?

  • try npm uninstall nodebb-theme-vanilla and then reinstall it again, it might install the version that satisfies the dependancy.

    Save changes made to vanilla too if need be 🙂

  • same result

  • @leksar try run ./nodebb upgrade
    paste error from th@ ?

  • leksar@ubuntu:~/nodebb$ sudo ./nodebb upgrade
    [sudo] password for leksar:
    no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory
    1. Bringing base dependencies up to date
    
    Error: The package [email protected] does not satisfy its siblings' peerDependencies requirements!
    
  • sounds like unlinking those plugins did nothing.

    I'm out of idea's but that was why it was complaining, maybe uninstall them if they aren't vital

    I dont use shoutbox or that other thingo

  • @Codejet said:

    I dont use shoutbox or that other thingo

    I'm not using them too, just tried for some time. The weird thing is that even uninstalling doesn't help. I would remove them manually, if there is a way.


Suggested Topics


  • Docker image update

    General Discussion
    0 Votes
    1 Posts
    67 Views

    Does anyone know how I can check when this will be updated please?

    Docker

    favicon

    (hub.docker.com)

    I'm using Elest.io to manage my NodeBB installation and I'm looking to update to the newest version.

    Thanks.

  • 1 Votes
    2 Posts
    169 Views

    @venkat Gotta be more specific with your problem. Someone may be able to help from this forum. Try opening an issue on github, but you'll have to describe your problem.

  • Error on Schema Update

    General Discussion
    0 Votes
    2 Posts
    1k Views

    @scottalanmiller said:

    component-emitter

    npm install component-emitter

    That did it, never mind,

  • 0 Votes
    3 Posts
    1k Views

    @psychobunny said:

    I recently got Windows 10

    Does that mean we're going to lose Windows XP support?

    I kid... I kid... 😆

    Edit: What are you doing up at 5:30am :suspect:

  • -1 Votes
    4 Posts
    2k Views

    Hi @Netto-Hikari, thanks for your feedback about our upgrade process 😄 We definitely try to make the upgrade process fluid and straightforward, but if files have been changed, then yes, there will be problems as git will not know how to handle changed files.

    Re:

    When it comes to upgrades, I just simply follow the docs and it always says that I have to commit the changes before.

    Did you mean Step 3? As far as I know, the only thing we ask admins to do before upgrading is back up their data. If you have never changed any of the core files, git should never complain.

    If this ever happens, and you are absolutely sure you didn't change anything, then you are advised to run the following:

    $ git fetch # to grab the latest code (but not apply it) $ git reset --hard origin/v0.5.x # force your local files to match the NodeBB repository *EXACTLY* $ ./nodebb upgrade # then proceed with upgrade as usual

    ^ Hooray, more unsolicited advice from strangers on the internet 😄

    After running those commands, future attempts to git pull should not have git complain.