new update/upgrade script, ready for testing

surger13

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

want to try the script again?

I did. Unfortunately, no change.
but thanks for your efforts.

evroom

You can try adding the missing variables

$ sudo cat /etc/default/locale
:
LANGUAGE=de_DE.UTF-8
LC_ALL=de_DE.UTF-8
:

And / or do a reconfigure:

$ sudo dpkg-reconfigure locales

Make sure de_DE.UTF-8 UTF-8 is checked.
Tab to OK
Tab to OK

$ sudo reboot

evroom

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

yeh, the website with the file broke the download…

Version 3.0.13 only takes 2 minutes.
Strangely enough version 3.1.13 takes ages and causes a timeout / connection reset.
Perhaps a local issue, although I have 57Mbps download.

Is there a reason for 3.1.13 and not @latest ?
Dependencies perhaps ?
Not that I want or need it, just asking.

sdetweil

@evroom no… i need to handle it, can’t expect users to do stuff to make the script work…

sdetweil

@surger13 willing to send me the log again?

sdetweil

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

evroom

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

sdetweil

@evroom weird… the package.json says

"electron": "^3.0.13"

same as we have been running on for a couple years now

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

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.