Read the statement by Michael Teeuw here.
new update/upgrade script, ready for testing
-
@sdetweil I found it ;o)
-
@trividar there are two scripts referenced above
a new updated installer script, that hopefully fixes some of the problems reported
a brand new script that will do the update/upgrade to the next MM version when it comes out.
the current MM plan is to release a new version every 90 days (quarter)look thru the forums for how many people had trouble installing the update…
2.7 from 2.6, and 2.8 from 2.7… -
i updated the links in the 1st post to add .sh to the end of the script name to be consistent with the other two scripts
raspberry.sh install
fixuppm2.sh fix pm2 without having to do install (or u changed your mind)
and now
update-script.sh do all the work to update your current install to new code level -
@sdetweil said in new update/upgrade script, ready for testing:
bash -c “$(curl -sL https://www.dropbox.com/s/lxzwyzohg61sppu/upgrade-script.sh?dl=0)” apply
Hi,
I just ran your script and get the following errors:
error: pathspec ‘.github/stale.yml’ did not match any file(s) known to git.
error: pathspec ‘modules/default/calendar/vendor/ical.js/example_rrule.js’ did not match any file(s) known to git.
error: pathspec ‘modules/default/calendar/vendor/ical.js/examples/example_rrule.ics’ did not match any file(s) known to git.
error: pathspec ‘modules/default/calendar/vendor/ical.js/test/test12.ics’ did not match any file(s) known to git.
error: pathspec ‘modules/default/calendar/vendor/ical.js/test/test13.ics’ did not match any file(s) known to git.
error: pathspec ‘modules/default/calendar/vendor/ical.js/test/test14.ics’ did not match any file(s) known to git.
error: pathspec ‘modules/default/weather/providers/ukmetoffice.js’ did not match any file(s) known to git.
error: pathspec ‘modules/default/weather/providers/weathergov.js’ did not match any file(s) known to git.
error: pathspec ‘translations/sk.json’ did not match any file(s) known to git.
error: pathspec ‘translations/tlh.json’ did not match any file(s) known to git.
error: pathspec ‘vendor/css/font-awesome.css’ did not match any file(s) known to git.Any Ideas? I dont recall messing with any of those files.
Thanks
MW -
@MwMagicMirror can u send me the mm/installers/upgrade.log
Same userid as here at Gmail.com -
Those files are in the current GitHub repo.
-
This post is deleted! -
@sdetweil said in new update/upgrade script, ready for testing:
can u send me the mm/installers/upgrade.log
Tried using the your upgrade script. Current MM version 2.6.
Upgrade started - Tue Aug 20 21:51:16 EDT 2019 doing test run = true downloading dumpactivemodules script saving custom.css remote name = fetching latest revisions MagicMirror git pull failed restoring custom.css Upgrade ended - Tue Aug 20 21:51:17 EDT 2019 -
@Mykle1 can u do a git status, and git remote -v
In the MagicMirror folder
-
i added a check for the git remote not being set.
-
@Mykle1 but at least there is a log to look at!
-
@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$ -
@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
-
Yes Sam, that is what I meant by a manual installation. :-/
-
@Mykle1 cool. Thanks for the test. Updated script to handle
-
@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:
-
@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)
-
Understood, thanks. :-)
-
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
-
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
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login