new update/upgrade script, ready for testing

sdetweil

@evroom no… just issue the command on the commandline

npm install electron@3.0.13

Is this a pi 0?

ChrizZz

@sdetweil said in new update/upgrade script, ready for testing:

@surger13 ok, looks like we have to fight the manual way

do
cd ~/MagicMirror
git stash
git merge
npm install

took the manual way too because of the same probs. Now my Pi is downloading the electron v3.1.13 version with 3.01 kB/s. can I stop the installation process to update electron manually?

sdetweil

@ChrizZz I do not know

surger13

@sdetweil said in new update/upgrade script, ready for testing:

@surger13 ok, looks like we have to fight the manual way

do
cd ~/MagicMirror
git stash
git merge
npm install

the fight was an easy one. everything worked. just had to restore the custom.css from a backup.
thanks again Sam

evroom

@ChrizZz said in new update/upgrade script, ready for testing:

Now my Pi is downloading the electron v3.1.13 version with 3.01 kB/s.

It looks like github has problems. I also cannot download other stuff from it with proper speed or without running into a timeout. Perhaps local or depends on your ISP region.

ChrizZz

@evroom said in new update/upgrade script, ready for testing:

@ChrizZz said in new update/upgrade script, ready for testing:

Now my Pi is downloading the electron v3.1.13 version with 3.01 kB/s.

It looks like github has problems. I also cannot download other stuff from it with proper speed or without running into a timeout. Perhaps local or depends on your ISP region.

I started installing electron in a new terminal session and it is downloading now with 16 kB/s. Maybe a stupid decission, maybe not.

Current status: 45% downloaded in the new terminal session, 18.5% downloaded as part of the MM update.

//edit: I stopped the inital installation, downloaded the right electron file from a mirror and placed the zip file in the /home/pi/.cache/electron folder. After that I updated electron manually. It worked well and after that I started npm install of the new MM version again. Now everything is updated without waiting years to download the zip from Github.

bdream

@sdetweil Hi Sam, after weeks being off I saw availability of v2.10.0 :slightly_smiling_face:
I run your script ```
bash -c “$(curl -sL https://www.dropbox.com/s/lxzwyzohg61sppu/upgrade-script.sh?dl=0)” apply

Do I need to stop MM first or 'only' run the script in MagicMirror folder?

Mykle1

@bdream

Just open a new terminal and run the script. MM should not be running, I believe.

panos

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)” apply

MM 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

see here:
https://forum.magicmirror.builders/topic/11912/problem-with-updating-to-2-10-0-from-2-9-0-using-update-script/2

Any suggestion on how to update to 2.10?

sdetweil

@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