Read the statement by Michael Teeuw here.
new update/upgrade script, ready for testing
-
Can someone write a how to instruction for mac? Thanks a lot…
-
@trividar said in new update/upgrade script, ready for testing:
Can someone write a how to instruction for mac? Thanks a lot…
How to run the update/upgrade script? :-/
-
@Mykle1 sorry for the noob question! I tried it and I got just errors…
-
@trividar said in new update/upgrade script, ready for testing:
sorry for the noob question! I tried it and I got just errors…
No worries. :thumbsup:
When did you run it? I’ve just done it minutes ago and it works fine. @sdetweil has been working on it but I believe he has ironed out most, if not all of the kinks.
- So, when did you run it?
- Errors during the upgrade or after the upgrade?
- What were the errors?
-
@Mykle1 I will send it tomorrow and also what I have done! Thanks for your time
-
Well, I would think you have nothing to lose by running the upgrade script again. Simply open a new terminal and copy and paste the script into the terminal and press enter.
-
this is what I get:
> cd - >/dev/null > date +"Upgrade ended - %a %b %e %H:%M:%S %Z %Y" >>$logfile > else > echo It appears MagicMirror has not been installed on this system > echo please run the installer, "raspberry.sh" first > fi
Can it be because my path has the same folder name twice? /Users/s****/MagicMirror/MagicMirror
-
Hmm, perhaps. The installer may be looking for the MM installation inside /Users/s****/MagicMirror. Can you move the MagicMirror folder with the installation OUT of the containing MagicMirror folder. Rename the containing MagicMirror folder to something else and put the MagicMirror folder containing the MM installation here
/Users/s****/MagicMirror
and try again? -
@trividar yeh, he assumes MagicMirror is THE folder where things are installed…
-
Test runs fine…This is the result when I try to apply the log will be ```
code_textNo LSB modules are available. doing test run = false 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 there were merge errors error: The following untracked working tree files would be overwritten by merge: installers/dumpactivemodules.js Please move or remove them before you merge. Aborting Updating 500147e..b595cdd you should examine and resolve them using the command git log --oneline --decorate 500147e (grafted, HEAD -> master, tag: v2.9.0) Merge pull request #1776 from MichMich/develop restoring custom.css