Read the statement by Michael Teeuw here.
new update/upgrade script, ready for testing
-
A couple of quick questions…
-
The “UpdateNotification” module is able to detect that there is a new version of MM available. Is this logged somewhere or easily accessible from the command line? I’m interested in writing a script that can assess the new version, possibly run a ‘test upgrade’ and then send me a IFTTT or pushover notification that a new version is available and an upgrade test succeeded (or failed).
-
Is the new upgrade script bundled with MM yet? I thought that was the intent, but did not see it up through 2.10.x
-
-
@ember1205 the scripts were removed from the mm base. I maintain them on my github page https://github.com/sdetweil/MagicMirror_scripts
the update cycle is 90days, 1st of the month
if u look at my upgrade-script I check the versions using curl, line 173
-
@sdetweil said in new update/upgrade script, ready for testing:
Where’s a good place to discuss the scripts? I’m wondering how feasible and useful it might be to add to the upgrade-script.sh one.
-
@ember1205 you could create an issue on the repo
-
@sdetweil : Thank you for the great installer script ! it worked well on Raspberry Pi Zero W. I had issue with electron and dependencies but it did the job :)
-
N Nneuland referenced this topic on
-
Running the upgrade script to install v2.25.0 and I get the following result. The last time I hit a roadblock I screwed things up enough that I did a fresh install. What are the proper steps to correct this?
bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" apply Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libc-ares2 libjs-highlight.js libnode72 nodejs-doc Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: nodejs* 0 upgraded, 0 newly installed, 1 to remove and 20 not upgraded. After this operation, 919 kB disk space will be freed. (Reading database ... 106969 files and directories currently installed.) Removing nodejs (12.22.12~dfsg-1~deb11u4) ... Processing triggers for man-db (2.9.4-2) ... Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease Reading package lists... Done Reading package lists... Done Building dependency tree... Done Reading state information... Done ca-certificates is already the newest version (20210119). curl is already the newest version (7.74.0-1.3+deb11u7). gnupg is already the newest version (2.2.27-2+deb11u2). The following packages were automatically installed and are no longer required: libc-ares2 libjs-highlight.js libnode72 nodejs-doc Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 20 not upgraded. deb [arch=arm64 signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_20.x nodistro main Get:1 https://deb.nodesource.com/node_20.x nodistro InRelease [12.1 kB] Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease Get:4 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages [3,264 B] Fetched 15.4 kB in 1s (15.7 kB/s) Reading package lists... Done Reading package lists... Done Building dependency tree... Done Reading state information... Done Suggested packages: npm The following NEW packages will be installed: nodejs 0 upgraded, 1 newly installed, 0 to remove and 20 not upgraded. Need to get 0 B/148 kB of archives. After this operation, 919 kB of additional disk space will be used. Selecting previously unselected package nodejs. (Reading database ... 106907 files and directories currently installed.) Preparing to unpack .../nodejs_12.22.12~dfsg-1~deb11u4_armhf.deb ... Unpacking nodejs (12.22.12~dfsg-1~deb11u4) ... Setting up nodejs (12.22.12~dfsg-1~deb11u4) ... update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode Processing triggers for man-db (2.9.4-2) ... doing test run = false update log will be in /home/pi/MagicMirror/installers/upgrade.log Check current Node installation ... Node currently installed. Checking version number. Minimum Node version: v20.8.0 Installed Node version: v12.22.12 Node should be upgraded. A Node process is currently running. Can't upgrade. Please quit all Node processes and restart the update. running process(s) are pi 934 932 0 Sep14 ? 00:00:00 node ./node_modules/.bin/electron js/electron.js -
I rebooted, and for some reason, MM didn’t restart right away, so I ran the script . It got further but then has an issue upgrading npm
-
@gonzonia sheesh, SO much fun… nodejs says is works and use this process…
we asked for node 20 and got something which turned into node 12…
(but then it doesn’t)I JUST tested this on the latest raspian 64bit… (june this year)
can you post output of these two commands
uname -a
lsb_release -a -
@sdetweil I found the this thread and I tired running with “force” but I’m getting the same issue when it tries to update npm.
pi@MagicMirror2:~/MagicMirror $ uname -a Linux MagicMirror2 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linuxpi@MagicMirror2:~/MagicMirror $ lsb_release -a No LSB modules are available. Distributor ID: Raspbian Description: Raspbian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye -
@gonzonia lets try this
bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/uninstall_node.sh)"this should remove node
so node -v should fail
then lets manually install node20
bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/node20_install.sh)"then check node version
node -v
