new update/upgrade script, ready for testing

[sdetweil]

@Mykle1 but at least there is a log to look at!

[Mykle1]

@sdetweil said in new update/upgrade script, ready for testing:

can u do a git status, and git remote -v

It’s very likely that this was a manual installation of MM (in case that matters)

pop@E8300:~$ cd MagicMirror/
pop@E8300:~/MagicMirror$ git status
fatal: not a git repository (or any of the parent directories): .git
pop@E8300:~/MagicMirror$ git remote -v
fatal: not a git repository (or any of the parent directories): .git
pop@E8300:~/MagicMirror$ ^C
pop@E8300:~/MagicMirror$ 

[sdetweil]

@Mykle1 is it possible u might have downloaded the code as a zip file, instead of doing git clone?

Only way I can think of to get into this state

[Mykle1]

@sdetweil

Yes Sam, that is what I meant by a manual installation. :-/

[sdetweil]

@Mykle1 cool. Thanks for the test. Updated script to handle

[Mykle1]

@sdetweil said in new update/upgrade script, ready for testing:

Thanks for the test. Updated script to handle

I wish I would have waited for the updated script. I went ahead and installed a new MM because I couldn’t move forward with what I am doing. Again, thanks for your scripts. I will continue to use them. They’re awesome. :thumbsup:

[sdetweil]

@Mykle1 I think u did the right thing. The “handle” is to bail out gracefully if there is no git repo locally (zip file install doesn’t provide any path forward, that I have found)

[Mykle1]

@sdetweil

Understood, thanks. :-)

[sdetweil]

Added some reporting of current version and version upgrading to.

Also had path that did a live merge when u were just testing. Fixed that

[sdetweil]

another update… i was reporting ALL the files that changed between versions, but who cares (things are SUPPOSED the change!)… we only care if there is a conflict… fixed that