Read the statement by Michael Teeuw here.
new update/upgrade script, ready for testing
-
@bhepler said in new update/upgrade script, ready for testing:
but that index.lock file does exist
to git that means it is already running… on exit it cleans up…
should I add handling this error to the script?
I can tell if its there and git is not running.great feedback… thanks
-
@bhepler i added handling for the git lock file…
if git is NOT running, I erase the dangling lock file
if git IS running, and this is an APPLY run, i change the run back to test mode, and advise to correct the problem -
I just did another run of your upgrade script, Sam. All went well.
MM 2.8.0 --> 2.9.0
Ubuntu 16.04.6 (downgraded from 18.04) -
@Mykle1 on the 1st run, no modules were updated… there should have been a message in the log… i didn’t see it… did u see any this time??
-
Sorry, I was distracted here, Sam. I just emailed you the upgrade.log
-
@Mykle1 thanks… they(last night and today) actually look good
i did make one change, the merge results generated one LONE line… i added some formatting to make it readable -
@Mykle1 well, there is installed modules, and there is active modules…
i only update the ACTIVE (ie, not disabled: true) modules with package.json files
-
Understood. :thumbsup:
-
for some reason, it updates me to version 2.8.0, although it seems like version 2.9.0 has already been released.
MagicMirror installation successful!
magicmirror@2.8.0 install-fonts /home/pi/MagicMirror
cd fonts && npm install -
@bobwilliams can you show me the MagicMirror/installers/upgrade.log
or send it to me mail, same userid as here on gmail, thanks
