new update/upgrade script, ready for testing

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.

bdream

@sdetweil Hi Sam, after weeks being off I saw availability of v2.10.0 :slightly_smiling_face:
I run your script ```
bash -c “$(curl -sL https://www.dropbox.com/s/lxzwyzohg61sppu/upgrade-script.sh?dl=0)” apply

Do I need to stop MM first or 'only' run the script in MagicMirror folder?

Mykle1

@bdream

Just open a new terminal and run the script. MM should not be running, I believe.

panos

Guys, I’m little confused.
I currently running at v2.9 and I wish to upgrade to v2.10
If I run the command:
bash -c "$(curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/upgrade-script.sh)” apply

MM won’t update to v2.10

If I try the ‘traditional’ way 'git pull && npm install’ and ignore any changes that I make I receive the error:

The following untracked working tree files would be overwritten by merge: installers/dumpactivemodules.js

see here:
https://forum.magicmirror.builders/topic/11912/problem-with-updating-to-2-10-0-from-2-9-0-using-update-script/2

Any suggestion on how to update to 2.10?

sdetweil

@panos the official script has a bug. Erase that file and use the updated version.

See
https://forum.magicmirror.builders/topic/10859/new-update-upgrade-script-ready-for-testing

bdream

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

See
https://forum.magicmirror.builders/topic/10859/new-update-upgrade-script-ready-for-testing

Sam, your link is looping or I’m wrong.

Can you please provide the link to the right script again? Sorry I’m confused and not able to update the MM.

sdetweil

@bdream the 1st post of this topic has the commands

bdream

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

the 1st post of this topic has the commands

it works :thumbs_up:
Many thanks AGAIN Sam!

spitzlbergerj

@sdetweil thanks for your great work. Unfortunately it does not work for me with the script.

When I execute the script I get the following messages:

bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)"
the log will be /home/pi/MagicMirror/installers/upgrade.log
No LSB modules are available.
doing test run = true
update log will be in /home/pi/MagicMirror/installers/upgrade.log

saving custom.css
upgrading from version 2.9.0 to 2.10.0
fetching latest revisions
fatal: Couldn't find remote ref origin
MagicMirror git fetch failed
restoring custom.css

The log file also contains the following:

not english or locale not set, set git alias
alias git='LC_ALL=en_US.UTF-8 git'
remote name = github-desktop-darkniki origin
upgrading from version 2.9.0 to 2.10.0
fetching latest revisions
git fetch rc=128
MagicMirror git fetch failed

Should I update manually or is there another way with the script?

Thanks

Sepp

sdetweil

@spitzlbergerj well, thats a new one…

i try to find the upstream git repo this installation came from, and then get the changes from there,
cause I want to be able to test the application of the changes without breaking the local system.

can u do

git remote 
and
git remote -v

thanks… it should be one word, but it looks like two on your system