new update/upgrade script, ready for testing

sdetweil

@spitzlbergerj yes, please erase this file

~/MagicMirror/installers/dumpactivemodules.js

it was copied early by the official updater in error

evroom

It is always difficult creating something and having it run flawlessly on many different systems with their many different settings, some exotic :-)

One more thing I stumbled upon when googling:

shopt -s expand_aliases

Add this before the alias command, or just at the top of your script.
Seems to work.

spitzlbergerj

@sdetweil
OK, now I have another problem :disappointed_face: . The upgrade script ran and I think it upgraded some stuff.

At some point, I must have gotten my permissions mixed up. There were a number of directories that were root:root. Here there was Permission denied.

I have now corrected the owners. But now the upgrade script doesn’t run anymore, because it assumes that I am already on 2.10.

Can I force another upgrade?

sdetweil

@spitzlbergerj yes, change ‘apply’ to ‘force’

sdetweil

@evroom I decided to forget about alias altogether…

evroom

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

I decided to forget about alias altogether…

Of course, your script, your call.
Just keep it somewhere in the back of your head, should you stumble over it again in any way or form.
As I minimum I learned something new, including using alias in a script at all.

Thanks for the scripts and the help you provide to all users with fresh install and / or upgrade issues, including myself.

sdetweil

@evroom thanks for your help… I had learned about the shell options to expand aliases about 10 yrs ago, and forgot… my systems all run with it on.

spitzlbergerj

@sdetweil
now it worked, my MagicMirror is on the current version :smiling_face_with_open_mouth_smiling_eyes: :thumbs_up: .

Many, many thanks for your patient help. It was a somewhat more difficult birth. But the end is good and so everything

I have a lot of respect for you, who created such a complex script and patiently provides support. Thank you very much!

One last question:
During the update there was another message:

npm WARN deprecated @types/vfile-message@2.0.0: This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed.

Is there anything else I should do?

sdetweil

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

It was a somewhat more difficult birth. But the end is good

yes, sadly we tested for a few months and this didn’t happen… weird…

on the warnings… really nothing u can do as a user… the code author should update
but hasn’t…

spitzlbergerj

@sdetweil thank you very much again!