Read the statement by Michael Teeuw here.
new update/upgrade script, ready for testing
-
Just open a new terminal and run the script. MM should not be running, I believe.
-
Guys, I’m little confused.
I currently running at v2.9 and I wish to upgrade to v2.10
If I run the command:
bash -c "$(curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/upgrade-script.sh)” applyMM won’t update to v2.10
If I try the ‘traditional’ way 'git pull && npm install’ and ignore any changes that I make I receive the error:
The following untracked working tree files would be overwritten by merge: installers/dumpactivemodules.js
Any suggestion on how to update to 2.10?
-
@panos the official script has a bug. Erase that file and use the updated version.
See
https://forum.magicmirror.builders/topic/10859/new-update-upgrade-script-ready-for-testing -
@sdetweil said in new update/upgrade script, ready for testing:
See
https://forum.magicmirror.builders/topic/10859/new-update-upgrade-script-ready-for-testingSam, your link is looping or I’m wrong.
Can you please provide the link to the right script again? Sorry I’m confused and not able to update the MM.
-
@bdream the 1st post of this topic has the commands
-
@sdetweil said in new update/upgrade script, ready for testing:
the 1st post of this topic has the commands
it works :thumbs_up:
Many thanks AGAIN Sam! -
@sdetweil thanks for your great work. Unfortunately it does not work for me with the script.
When I execute the script I get the following messages:
bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" the log will be /home/pi/MagicMirror/installers/upgrade.log No LSB modules are available. doing test run = true update log will be in /home/pi/MagicMirror/installers/upgrade.log saving custom.css upgrading from version 2.9.0 to 2.10.0 fetching latest revisions fatal: Couldn't find remote ref origin MagicMirror git fetch failed restoring custom.css
The log file also contains the following:
not english or locale not set, set git alias alias git='LC_ALL=en_US.UTF-8 git' remote name = github-desktop-darkniki origin upgrading from version 2.9.0 to 2.10.0 fetching latest revisions git fetch rc=128 MagicMirror git fetch failed
Should I update manually or is there another way with the script?
Thanks
Sepp
-
@spitzlbergerj well, thats a new one…
i try to find the upstream git repo this installation came from, and then get the changes from there,
cause I want to be able to test the application of the changes without breaking the local system.can u do
git remote and git remote -v
thanks… it should be one word, but it looks like two on your system
-
@spitzlbergerj could u try this little script to see if I got it right?
curl -sL https://www.dropbox.com/s/80fevh39jme3iig/testlang.sh?dl=0 | bash
it will check the status of the 3 lang settings,
LANG=
LANGUAGE=
and LC_ALL= -
@sdetweil thanks for your Help. Here are the results
git remote github-desktop-darkniki origin git remote -v github-desktop-darkniki https://github.com/darkniki/MagicMirror.git (fetch) github-desktop-darkniki https://github.com/darkniki/MagicMirror.git (push) origin https://github.com/MichMich/MagicMirror.git (fetch) origin https://github.com/MichMich/MagicMirror.git (push)
and for the second post:
curl -sL https://www.dropbox.com/s/80fevh39jme3iig/testlang.sh?dl=0 | bash not english or locale not set, set git alias alias git='LC_ALL=en_US.UTF-8 git' Auf Branch master Ihr Branch ist zu 'origin/master' um 117 Commits hinterher, und kann vorgespult werden. (benutzen Sie "git pull", um Ihren lokalen Branch zu aktualisieren) Unversionierte Dateien: (benutzen Sie "git add <Datei>...", um die Änderungen zum Commit vorzumerken) core installers/dumpactivemodules.js nichts zum Commit vorgemerkt, aber es gibt unversionierte Dateien (benutzen Sie "git add" zum Versionieren)
I hope this helps
Regards
Sepp