Read the statement by Michael Teeuw here.
Unable to update
-
@eugenelai sounds like you downloaded the mirror manually and didn’t use git clone.
-
Sorry I get the same error message if I use sudo as well. I guess i’ll backup all the files I’ve changed do a
git init
then see what happens.@strawberry-3.141
Nope did the automatic install. -
@eugenelai said in Unable to update:
Sorry I get the same error message if I use sudo as well.
Ok, but I said you should NOT have to use sudo to run those commands
-
Yeah still doesn’t work. I’ve done
git init
then tried bothgit pull && npm install
with and without sudo and I get the following:pi@MagicMirrorPi:~ $ cd MagicMirror pi@MagicMirrorPi:~/MagicMirror $ sudo git pull && npm install fatal: No remote repository specified. Please, specify either a URL or a remote name from which new revisions should be fetched. pi@MagicMirrorPi:~/MagicMirror $
-
Personally, if this was me, I would rename my existing MagicMirror folder, install the new MagicMirror via git clone, run
npm install
in the new MagicMirror folder, then move what I want from the old MagicMirror installation into the new installation.NO SUDO necessary
-
@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!