Update to v2.9.0 fail

sdetweil

pi@MagicMirror:~/MagicMirror $ echo $LC_ALL
de_DE.UTF-8

bingo… things you learn!..

LC_ALL overrides LANG or LANGUAGE=

I just have to fix my alias…

would u be willing to test the fix… no changes to your local running system

package-lock.json should exist

ls package-lock.json

then

bash -c "$(curl -sL https://www.dropbox.com/s/lxzwyzohg61sppu/upgrade-script.sh?dl=0)" force

when u see the message about saving files, just hit ctrl-c to exit

bdream

@sdetweil said in Update to v2.9.0 fail:

when u see the message about saving files, just hit ctrl-c to exit

I was to slow for hitting ctrl-c :nerd_face:

As this is a huge of lines my buffer is to small.
Is there a log or is there no interest to u of the outcome?

sdetweil

@bdream yes the install.log

but it should have waited for you to reply about writing over package-lock.json

hm… if package.lock.json does NOT exist

then create it

touch package-lock.json

bdream

@sdetweil said in Update to v2.9.0 fail:

hm… if package.lock.json does NOT exist

nono, it did exist

pi@MagicMirror:~/MagicMirror $  ls pack*
package.json  package-lock.json

but the script run fast

bash -c "$(curl -sL https://www.dropbox.com/s/lxzwyzohg61sppu/upgrade-script.sh?dl=0)" force

what path I can find the install.log?

sdetweil

@bdream sorry, not install… upgrade.log

doing test run = false
update log will be in /home/pi/MagicMirror/installers/upgrade.log

on the package-lock.json… it is the same as the update… thus why it didn’t stop

could edit it an add a space someplace

bdream

@sdetweil upgrade.log is here from …force… no it isn’t.
I can’t copy the 2738 lines in here.
How can I bring it to you?

And what does this mean?

on the package-lock.json… it is the same as the update… thus why it didn’t stop

could edit it an add a space someplace

sdetweil

@bdream said in Update to v2.9.0 fail:

upgrade.log is here from …force… no it isn’t.
I can’t copy the 2738 lines in here.

you can email it , same userid as here on gmail

And what does this mean?

on the package-lock.json… it is the same as the update… thus why it didn’t stop

could edit it an add a space someplace

the upgrade should have stopped at the package-lock.json file, just like before…
but it didn’t… so I looked back at the 2.9.0 package being installed, and it has a package-lock.json file…

so, the one now on the disk is the new one… and a git status will show it hasn’t changed…

so, we could MAKE it be different, by using a text editor (like the one you use on the config.js file)
and add 1 space character (hit the spacebar)
and then save it… then it will be different

bdream

got u mail from me? I would send you logs then.

@sdetweil said in Update to v2.9.0 fail:

so, we could MAKE it be different, by using a text editor (like the one you use on the config.js file)
and add 1 space character (hit the spacebar)
and then save it… then it will be different

Is this you ask me to do? and rund your script again to see if it works now?

sdetweil

@bdream i got one mail and replied. have not got any more

yes, was a way to test. if u can

bdream

@sdetweil said in Update to v2.9.0 fail:

if u can

Got it

Upgrade started - Mi Okt 16 20:03:22 CEST 2019
user requested to apply changes
doing test run = false

saving custom.css
not english or locale not set, set git alias
alias egrep='egrep --color=auto'
alias fgrep='fgrep --color=auto'
alias git='LC_ALL=en_US.UTF-8 git'
alias grep='grep --color=auto'
alias ls='ls --color=auto'
remote name = origin
local version 2.9.0 already same as master 2.9.0
restoring custom.css
removing git alias
Upgrade ended - Mi Okt 16 20:03:22 CEST 2019

there is no statement about the package-lock.json where I added spaces and saved it.

Seems it works fine :grinning_face_with_smiling_eyes:

One question I have now.
Would it make sense changing the guide for update MM using your script instead of git pull && npm install?
Or is this only a option in case of failure?