new update/upgrade script, ready for testing

[sdetweil]

@evroom i don’t on the npm install… expect it to work… as we’ve been thru test on this for a long time.

[sdetweil]

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

do

cd ~/MagicMirror
git stash
git merge
npm install

[evroom]

@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"

[sdetweil]

@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

[evroom]

@sdetweil

~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.

[evroom]

@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]

@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