Read the statement by Michael Teeuw here.
new update/upgrade script, ready for testing
-
@evroom Is there a reason for 3.1.13 and not @latest ?
should be 3.0.13
yes, V7 doesn’t run right,
v6 needs some other changes,V3 is the last one on armv6 (pi 0)
-
@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. -