Read the statement by Michael Teeuw here.
Unable to update
-
@Mykle1 Yes that would be the easiest way to do it!
-
-
@eugenelai It will save you endless headaches…
-
Well, tried renaming, then installing a new MagicMirro via git clone and then run npm install and its totally gone tits up.
Ah well just going to wipe the SD card and start again. Thankfully have all my stuff backed up.
-
Hopefully it’s not too late to help save you (and others) some time and worry.
I just updated my install using ‘git pull && npm install’ and it actually aborts if it detects the update will overwrite files you’ve changed (pretty awesome feature imo).
Also, you don’t need to copy your main folder or even move any files elsewhere - all you need to do is rename the files it says would be overwritten with the update, and you can leave them in the same folder.
For instance, it said my main.css had changes and would be overwritten. I just renamed it to main2.css and left it where it was (and did similarly to a few other files).After updating to the latest MM, I just went to the css folder, opened up that file (sudo nano main2.css), then saved it overwriting the newly updated version (saved to main.css).
That’s all I did for the few files I had customized and upon restart, all of my changes were present. Good luck! -
After every MagicMirror update i have to set up the MagicMirror from scratch.
It crashed my system completely.
So if you dont want to have hours of time and headache, simply do not update your system.
I had the same problem when i did the last update.
My journey yesterday -
@kidddrock said in Unable to update:
Hopefully it’s not too late to help save you (and others) some time and worry.
I just updated my install using ‘git pull && npm install’ and it actually aborts if it detects the update will overwrite files you’ve changed (pretty awesome feature imo).
Also, you don’t need to copy your main folder or even move any files elsewhere - all you need to do is rename the files it says would be overwritten with the update, and you can leave them in the same folder.
For instance, it said my main.css had changes and would be overwritten. I just renamed it to main2.css and left it where it was (and did similarly to a few other files).After updating to the latest MM, I just went to the css folder, opened up that file (sudo nano main2.css), then saved it overwriting the newly updated version (saved to main.css).
That’s all I did for the few files I had customized and upon restart, all of my changes were present. Good luck!Actually it wasn’t a matter of overwriting files. That I could figure out. I couldn’t even do a git pull During the automatic installation a .git file wasn’t created or initialised. Worked out in the end thought… Just a massive ball ache.
