Updating 6db61b4..de57daa

sdetweil

@mwel1977 said in Updating 6db61b4..de57daa:

the swannie

swannie river

up the river…
http://www.musicanet.org/robokopp/usa/waydownu.htm

dazza120

@mwel1977 yep UK local slang, anyway I’ve sorted it now I downloaded the Magic Mirror from github on the Pi, unzipped it and then copied the whole folder to the module default location and over wrote everything, it was missing a lot of files for some reason. Anyway enough said it’s working like it should now 👌🏾

idoodler

@mwel1977 The vulnerabilities needs to be fixed by the module developer. Thats not your responsibility, you can just ignore them.

Because of the Node.js version: You don’t have to update to a newer version of Node.js. Latest isn’t always the greatest, there are some known compatibility issues with v11.

rosenm

this one helped me:

https://forum.magicmirror.builders/topic/4418/update/3

Screwyoudriver

I renamed the old folder and did a fresh installation. Half an hour of work if you use the old config and css.

icephreaq

I do have an active internet connection. I typically admin my mirror through SSH from a separate Linux machine and I’m able to connect to the mirror and update other items without issue. git status gives the following.

On branch master
Your branch is behind 'origin/master' by 124 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   fonts/package-lock.json
	modified:   package-lock.json
	modified:   package.json
	modified:   vendor/package-lock.json

Untracked files:
  (use "git add <file>..." to include in what will be committed)

	core
	nohup.out

no changes added to commit (use "git add" and/or "git commit -a")

bhepler

@icephreaq - Give this a try:

cd ~/MagicMirror
git stash
git pull
npm install

Also, @costascontis - You shouldn’t run the git commands as sudo. You may end up screwing up your permissions on the files pulled down from git.

icephreaq

I ended up removing all instances of package-lock.json and ran git pull and was able to successfully update. Thanks for everyone’s input on this!

MWel1977

@idoodler Okay. Thanks for that answer! hehehehe…
Anyway my MM2 is working like it should be after I moved that folder and did the git pull again.
But about the steps to take on how to update a module or a dependency or Node.js in my case… is that written down somewere here on the forum?
Like… all the steps someone needs to take in order to keep MM2 in shape?

dazza120

@mwel1977 get yourself MMM-RemoteControl and MMM-RemoteRepositories to get those modules updated easily, it will check through them and update automagically when you go into the html page