Read the statement by Michael Teeuw here.
new update/upgrade script, ready for testing
-
@sdetweil
Okay, just that you know that my current 2.8.0 to 2.10.0 upgrade is trying to get 3.1.13.> electron@3.1.13 postinstall /home/pi/MagicMirror/node_modules/electron > node install.js Downloading tmp-21342-0-electron-v3.1.13-linux-armv7l.zip [==========================> ] 61.8% of 45.65 MB (720.69 B/s)This was in the log for the 2.9.0 to 2.10.0 upgrade:
> electron@3.1.13 postinstall /home/pi/MagicMirror/node_modules/electron > node install.js Downloading tmp-27972-0-electron-v3.1.13-linux-armv7l.zip Error: read ECONNRESET /home/pi/MagicMirror/node_modules/electron/install.js:49 throw err ^ Error: read ECONNRESET at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27)Do you catch and evaluate the output or only the exit value?
-
@evroom weird… the package.json says
"electron": "^3.0.13"same as we have been running on for a couple years now
-
@evroom i don’t on the npm install… expect it to work… as we’ve been thru test on this for a long time.
-
@surger13 ok, looks like we have to fight the manual way
do
cd ~/MagicMirror git stash git merge npm install -
@sdetweil said in new update/upgrade script, ready for testing:
weird… the package.json says
Which exact package.json would that be?
Perhaps mine tells to use 3.1.13?Although:
pi@raspberrypi:~ $ grep electron ~/MagicMirror/package.json "main": "js/electron.js", "electron": "^3.0.13" -
@evroom ah, it say CLOSE TO 3.0.13 (the hat char), not exactly 3.0.13
so, do the manual step
npm install electron@3.0.13
-
~version “Approximately equivalent to version”, will update you to the next patch version.
^version Will update you to the next minor version.
version Will update you to the exact given version.
-
@sdetweil
Sam, shall I update my ~/MagicMirror/package.json file and try again?Edit:
Just did.
It says I am on 2.10.0 already, even though it was interrupted on the electro download.How can I force the upgrade or make it believe 2.9.0 is still active?
In the package.json file?Edit 2:
Changed from 2.10.0 to 2.9.0 and now it is running. -
-
@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 installtook 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?
-
@ChrizZz I do not know
-
@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 installthe fight was an easy one. everything worked. just had to restore the custom.css from a backup.
thanks again Sam -
@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.
-
@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.
-
@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)” applyDo I need to stop MM first or 'only' run the script in MagicMirror folder? -
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
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