Read the statement by Michael Teeuw here.
new update/upgrade script, ready for testing
-
pi@MagicMirrorPi:~/MagicMirror $ locale LANG=de_DE.UTF-8 LANGUAGE= LC_CTYPE="de_DE.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL= pi@MagicMirrorPi:~/MagicMirror $ -
@surger13 wild… a THIRD way to indicate language setting
want to try the script again?
-
@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. -
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 localesMake sure de_DE.UTF-8 UTF-8 is checked.
Tab to OK
Tab to OK$ sudo reboot -
@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. -
@evroom no… i need to handle it, can’t expect users to do stuff to make the script work…
-
@surger13 willing to send me the log again?
-
@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. -
-
@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
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