Update to v2.9.0 fail

bdream

@sdetweil said in Update to v2.9.0 fail:

erase package-lock.json

done!
seems update is working now :grinning_face:

pi@MagicMirror:~/MagicMirror $ bash -c -i  "$(curl -sL https://www.dropbox.com/s/lxzwyzohg61sppu/upgrade-script.sh?dl=0)" apply
doing test run = false
update log will be in /home/pi/MagicMirror/installers/upgrade.log

saving custom.css
upgrading from version 2.8.0 to 2.9.0
fetching latest revisions
updating MagicMirror runtime, please wait

> electron@3.0.13 postinstall /home/pi/MagicMirror/node_modules/electron
> node install.js

Downloading tmp-5207-1-SHASUMS256.txt-3.0.13
[============================================>] 100.0% of 4.79 kB (4.79 kB/s)

> magicmirror@2.9.0 install /home/pi/MagicMirror
> cd vendor && npm install

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

audited 220 packages in 12.241s
found 5 vulnerabilities (4 low, 1 high)
  run `npm audit fix` to fix them, or `npm audit` for details

> magicmirror@2.9.0 postinstall /home/pi/MagicMirror
> sh untrack-css.sh && sh installers/postinstall/postinstall.sh && npm run install-fonts

We'll remove from the repository the css/custom.css
This script apply git update-index --skip-worktree css/custom.css
rm 'css/custom.css'
MagicMirror installation successful!

> magicmirror@2.9.0 install-fonts /home/pi/MagicMirror
> cd fonts && npm install

audited 1 package in 1.629s
found 0 vulnerabilities

npm WARN grunt-stylelint@0.11.1 requires a peer of stylelint@^10.0.0 but none is installed. You must install peer dependencies yourself.

added 173 packages from 113 contributors, removed 132 packages, updated 181 packages, moved 1 package and audited 3475 packages in 1071.546s
found 28 vulnerabilities (1 low, 1 moderate, 26 high)
  run `npm audit fix` to fix them, or `npm audit` for details
processing dependency changes for active modules with package.json files

processing for module MMM-Carousel please wait
----------------------------------
audited 859 packages in 17.666s
found 2 high severity vulnerabilities
  run `npm audit fix` to fix them, or `npm audit` for details
processing complete for module MMM-Carousel

processing for module MMM-PublicTransportHafas please wait
----------------------------------
audited 41 packages in 2.153s
found 0 vulnerabilities

processing complete for module MMM-PublicTransportHafas

processing for module MMM-PublicTransportHafas please wait
----------------------------------
audited 41 packages in 3.251s
found 0 vulnerabilities

processing complete for module MMM-PublicTransportHafas

processing for module MMM-PublicTransportHafas please wait
----------------------------------
audited 41 packages in 3.956s
found 0 vulnerabilities

processing complete for module MMM-PublicTransportHafas

restoring custom.css

  pm2 start mm

…and it looks GOOD! :rolling_on_the_floor_laughing:
It’s great after such a … work? … getting it solved.

Thank you sooo much. On my own I would install from scatch :frowning_face: and this is nothing I can bring to my family.

and here you asked

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

would say this is one of the first thing I do installing Raspian :grimacing_face:

sdetweil

@bdream said in Update to v2.9.0 fail:

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