Read the statement by Michael Teeuw here.
Failed Update
-
@sdetweil I did this
sudo apt-get remove nodejs npm -y
hash -r
which node
which nif which n response with empty then do
sudo apt-get install n
once n responds then
sudo n 20.8.0 --arch armv7l
hash -r
node -vThen both scripts and it went through!
-
@DarkV said in Failed Update:
–arch armv7l
awesome… it was that sneaky little --arch parm…
fixing upgrade script now . sorry for your troubles
-
@sdetweil No worries, thanks you for your time
-
@DarkV any chance you still have the os image file you are running
the info says (from the upgrade.log)
6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseyeonly one I can find online says
6.1.21-v7+trying to test fix for the problem you encountered.
if you still have the image file can you give me its name…
also, what pi is this, 3 or 4?
thanks| edit: was able to make one
| install bullseye armhf
| edit /boot/config.txt
add
arm_64bit=1then u will boot 64bit kernel, (seen with uname -a, aarch64)
Linux raspberrypi4 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linuxand have 32 bit runtime (seen with file /bin/bash
/bin/bash: ELF 32-bit LSB executable -
@sdetweil
Sam, I did an update yesterday and found Node 20.8 not working on my raspbian bullseye install.
I had an issue mentioned by someone else here before referring a missing GLIBCXX_3.4.26 file.
I needed to purge and install node 18.x. Then it worked.
Possible that this happens for more users with Raspbian
Bullseye.
I see your upgrade script requests Node 20.8.
Not sure if that may be an issue for other people as well? -
@lavolp3 can u send me the ~/MagicMirror/installers/upgrade.log
so I can see what happened…
same userid at gmail
-
@lavolp3 I check for buster and downgrade to node 18… not bullseye…
interested to see the log…
-
@sdetweil Sorry I have BUSTER installed. My mistake.
Here the lastlog
Upgrade started - Wed Nov 1 10:25:06 CET 2023 system is Linux magicmirror 5.10.103-v7+ #1529 SMP Tue Mar 8 12:21:37 GMT 2022 armv7l GNU/Linux the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster n (node version manager tool) not installed, doing test run, install skipped doing test run = true, NO updates will be applied! Check current Node installation ... Node currently installed. Checking version number. Minimum Node version: v18.18.0 Installed Node version: v16.20.2 Node should be upgraded. Upgrade started - Wed Nov 1 10:45:19 CET 2023 system is Linux magicmirror 5.10.103-v7+ #1529 SMP Tue Mar 8 12:21:37 GMT 2022 armv7l GNU/Linux user requested to force apply changes the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster node not installed, trying via apt-get Reading package lists... Building dependency tree... Reading state information... nodejs is already the newest version (20.9.0-1nodesource1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. npm not installed, trying via apt-get npm NOT installed now, install now Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: npm : Depends: nodejs (>= 6.11~) Depends: node-abbrev (>= 1.1.1~) but it is not going to be installed Depends: node-ansi-regex (>= 3.0~) but it is not going to be installed Depends: node-ansistyles (>= 0.1.3~) but it is not going to be installed Depends: node-aproba (>= 1.2~) but it is not going to be installed Depends: node-archy (>= 1.0~) but it is not going to be installed Depends: node-cacache (>= 10.0.4~) but it is not going to be installed Depends: node-bluebird (>= 3.5.1~) but it is not going to be installed Depends: node-call-limit (>= 1.1~) but it is not going to be installed Depends: node-chownr (>= 1.0.1~) but it is not going to be installed Depends: node-config-chain (>= 1.1.11~) but it is not going to be installed Depends: node-detect-indent (>= 5.0~) but it is not going to be installed Depends: node-detect-newline (>= 2.1~) but it is not going to be installed Depends: node-editor (>= 1.0~) but it is not going to be installed Depends: node-fs-vacuum (>= 1.2.10~) but it is not going to be installed Depends: node-fs-write-stream-atomic (>= 1.0.10~) but it is not going to be installed Depends: node-glob (>= 7.1.2~) but it is not going to be installed Depends: node-graceful-fs (>= 4.1.11~) but it is not going to be installed Depends: node-has-unicode (>= 2.0.1~) but it is not going to be installed Depends: node-hosted-git-info (>= 2.6~) but it is not going to be installed Depends: node-iferr (>= 0.1.5~) but it is not going to be installed Depends: node-inflight (>= 1.0.6~) but it is not going to be installed Depends: node-inherits (>= 2.0.3~) but it is not going to be installed Depends: node-ini (>= 1.3.5~) but it is not going to be installed Depends: node-npm-package-arg but it is not going to be installed Depends: node-promzard but it is not going to be installed Depends: node-jsonstream (>= 1.3.2~) but it is not going to be installed Depends: node-json-parse-better-errors (>= 1.0.1~) but it is not going to be installed Depends: node-lazy-property (>= 1.0~) but it is not going to be installed Depends: node-libnpx (>= 10.0.1~) but it is not going to be installed Depends: node-lockfile (>= 1.0.3~) but it is not going to be installed Depends: node-lru-cache (>= 4.1.1~) but it is not going to be installed Depends: node-mississippi (>= 3.0~) but it is not going to be installed Depends: node-mkdirp (>= 0.3.3) but it is not going to be installed Depends: node-move-concurrently (>= 1.0.1~) but it is not going to be installed Depends: node-nopt but it is not going to be installed Depends: node-normalize-package-data (>= 2.4~) but it is not going to be installed Depends: node-gyp (>= 3.6.2~) but it is not going to be installed Depends: node-resolve-from (>= 4.0~) but it is not going to be installed Depends: node-encoding but it is not going to be installed Depends: node-errno but it is not going to be installed Depends: node-npmlog (>= 4.1.2~) but it is not going to be installed Depends: node-once (>= 1.4~) but it is not going to be installed Depends: node-opener (>= 1.4.3~) but it is not going to be installed Depends: node-osenv (>= 0.1.5~) but it is not going to be installed Depends: node-path-is-inside (>= 1.0.2~) but it is not going to be installed Depends: node-promise-inflight (>= 1.0.1~) but it is not going to be installed Depends: node-ansi but it is not going to be installed Depends: node-qw (>= 1.0.1~) but it is not going to be installed Depends: node-read (>= 1.0.7~) but it is not going to be installed Depends: node-read-package-json (>= 2.0.13~) but it is not going to be installed Depends: node-request (>= 2.83~) but it is not going to be installed Depends: node-retry (>= 0.10.1~) but it is not going to be installed Depends: node-rimraf (>= 2.6.2~) but it is not going to be installed Depends: node-safe-buffer (>= 5.1.1~) but it is not going to be installed Depends: node-semver (>= 5.5~) but it is not going to be installed Depends: node-sha (>= 2.0.1~) but it is not going to be installed Depends: node-slide (>= 1.1.6~) but it is not going to be installed Depends: node-sorted-object (>= 2.0.1~) but it is not going to be installed Depends: node-from2 but it is not going to be installed Depends: node-stream-iterate but it is not going to be installed Depends: node-ssri (>= 5.2.4~) but it is not going to be installed Depends: node-strip-ansi (>= 4.0~) but it is not going to be installed Depends: node-tar (>= 4.4~) but it is not going to be installed Depends: node-text-table (>= 0.2~) but it is not going to be installed Depends: node-uid-number (>= 0.0.6~) but it is not going to be installed Depends: node-unique-filename (>= 1.1~) but it is not going to be installed Depends: node-unpipe (>= 1.0~) but it is not going to be installed Depends: node-boxen (>= 1.2.1~) but it is not going to be installed Depends: node-import-lazy but it is not going to be installed Depends: node-is-npm (>= 1.0~) but it is not going to be installed Depends: node-latest-version (>= 3.0~) but it is not going to be installed Depends: node-semver-diff (>= 2.0~) but it is not going to be installed Depends: node-xdg-basedir (>= 3.0~) but it is not going to be installed Depends: node-validate-npm-package-name (>= 3.0~) but it is not going to be installed Depends: node-which (>= 1.3~) but it is not going to be installed Depends: node-wrappy (>= 1.0.2~) but it is not going to be installed Depends: node-write-file-atomic (>= 2.3~) but it is not going to be installed E: Unable to correct problems, you have held broken packages. doing test run = false Check current Node installation ... Node currently installed. Checking version number. forcing low Node version Minimum Node version: v18.18.0 Installed Node version: V1.0.0 Node should be upgraded.That was the last failed upgrade. Node V1.0.0 lol. Node 20 was installed.
After that I manually purged Node, installed Node 18 and did thenpm run install-mm -
@lavolp3 ok, can you do
sudo apt update --fix-missing sudo apt install -fwatch out for node changing…
-
@sdetweil Sam, sorry for the confusion, everything is working. A said I had installed node 18 and then it all worked. I didn’t need help, just wanted to point out that node 20 seems to not be working with some systems. But as I see you got that covered in your script.
