Updating to v2.2.0...

[bhepler]

@stephenmelody Empty responses are good. That usually means no problems. Once you have your command line back, you’re free to proceed.

[stephenmelody]

it came back within a second… when you say proceed… what’s next?

[bhepler]

@stephenmelody Next step is to run your mirror and make sure nothing has changed.

[stephenmelody]

nothing has changed, I’m still 86 commits behind on the master branch.

[stephenmelody]

Am I doing it in the right folder? Is the command correct? I’m getting the same response no matter what folder i’m in within the MM install

[stephenmelody]

Can anyone help? I get the same message no matter what I try to do.

[mochman]

Just trying to cover all the bases here, but are you on the master branch? You can run git branch to see. It should say something like:

pi@Magic-Mirror:~/ $ cd MagicMirror
pi@Magic-Mirror:~/MagicMirror $ git branch
* master

The asterisk denotes which branch is your current one.
If for some reason you’re not on the master branch use git checkout master to switch back to the master branch.
Then try running git pull and see if anything happens. Hopefully you get a list of files that have been changed. If not, and you don’t see an error messages try git pull -v to see what errors (if any) you are getting.
Hopefully that all works out, then you can just run npm install and you should be all set.

Good luck.

[stephenmelody]

Thanks @mochman

This is what I’m getting now… any clues??


[mochman]

okay, try running
rm -f ~/MagicMirror/.git/index.lock
then try git pull again. Hopefully you’ll see more than:
Updating b799609..20823bf

[stephenmelody]

Thank you so much!! That seems to have fixed it!!