Bonjour,
Depuis plusieurs mois, les dépendances de mon ESP Easy sont mortes. Voici le log à l’installation:
Début de l'installation
--2022-02-02 08:10:35-- https://raw.githubusercontent.com/lunarok/jeedom_nodejs/master/nodejs.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.108.133, 185.199.109.133, 185.199.110.133, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.108.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1552 (1.5K) [text/plain]
Saving to: 'dependencies.sh'
0K . 100% 2.39M=0.001s
2022-02-02 08:10:35 (2.39 MB/s) - 'dependencies.sh' saved [1552/1552]
dependencies.sh: 3: [: espeasy: unexpected operator
Version actuelle : 12
Hit:1 http://archive.raspberrypi.org/debian stretch InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Hit:3 https://deb.nodesource.com/node_12.x stretch InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
lsb-release is already the newest version (9.20161125+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 23 not upgraded.
dependencies.sh: 29: dependencies.sh: [[: not found
KO, version obsolète à upgrader
Suppression du Nodejs existant et installation du paquet recommandé
Reading package lists...
Building dependency tree...
Reading state information...
Package 'npm' is not installed, so not removed
The following packages will be REMOVED:
nodejs*
0 upgraded, 0 newly installed, 1 to remove and 23 not upgraded.
After this operation, 85.8 MB disk space will be freed.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 66194 files and directories currently installed.)
Removing nodejs (12.22.10-1nodesource1) ...
Processing triggers for man-db (2.7.6.1-2) ...
dependencies.sh: 38: [: armv7l: unexpected operator
Utilisation du dépot officiel
## Installing the NodeSource Node.js 14.x repo...
## Populating apt-get cache...
+ apt-get update
Hit:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Hit:2 http://archive.raspberrypi.org/debian stretch InRelease
Hit:3 https://deb.nodesource.com/node_12.x stretch InRelease
Reading package lists...
## Confirming "stretch" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_14.x/dists/stretch/Release'
## Adding the NodeSource signing key to your keyring...
+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | gpg --dearmor | tee /usr/share/keyrings/nodesource.gpg >/dev/null
## Creating apt sources list file for the NodeSource Node.js 14.x repo...
+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_14.x stretch main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_14.x stretch main' >> /etc/apt/sources.list.d/nodesource.list
## Running `apt-get update` for you...
+ apt-get update
Hit:1 http://archive.raspberrypi.org/debian stretch InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Get:3 https://deb.nodesource.com/node_14.x stretch InRelease [4585 B]
Get:4 https://deb.nodesource.com/node_14.x stretch/main armhf Packages [780 B]
Fetched 5365 B in 3s (1590 B/s)
Reading package lists...
## Run `sudo apt-get install -y nodejs` to install Node.js 14.x and npm
## You may also need development tools to build native addons:
sudo apt-get install gcc g++ make
## To install the Yarn package manager, run:
curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --dearmor | sudo tee /usr/share/keyrings/yarnkey.gpg >/dev/null
echo "deb [signed-by=/usr/share/keyrings/yarnkey.gpg] https://dl.yarnpkg.com/debian stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt-get update && sudo apt-get install yarn
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
nodejs
0 upgraded, 1 newly installed, 0 to remove and 23 not upgraded.
Need to get 23.4 MB of archives.
After this operation, 117 MB of additional disk space will be used.
Get:1 https://deb.nodesource.com/node_14.x stretch/main armhf nodejs armhf 14.19.0-1nodesource1 [23.4 MB]
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Fetched 23.4 MB in 9s (2361 kB/s)
Selecting previously unselected package nodejs.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 61330 files and directories currently installed.)
Preparing to unpack .../nodejs_14.19.0-1nodesource1_armhf.deb ...
Unpacking nodejs (14.19.0-1nodesource1) ...
Setting up nodejs (14.19.0-1nodesource1) ...
Processing triggers for man-db (2.7.6.1-2) ...
ln: failed to create symbolic link '/usr/bin/nodejs': File exists
Version actuelle : v14.19.0
npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EINTEGRITY: sha512-OvNTHeHlQ0BJFyQnUquSMwp0FrkrHD5HpxXMr9Q/5/dPVA9ArajgORbw2bUQTWuQzvmb2KWT2Wm/PcOAIM50Wg== integrity checksum failed when using sha512: wanted sha512-OvNTHeHlQ0BJFyQnUquSMwp0FrkrHD5HpxXMr9Q/5/dPVA9ArajgORbw2bUQTWuQzvmb2KWT2Wm/PcOAIM50Wg== but got sha512-z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg==. (0 bytes)
npm WARN registry Using stale data from https://registry.npmjs.org/ due to a request error during revalidation.
npm ERR! code EINTEGRITY
npm ERR! errno EINTEGRITY
npm ERR! Invalid response body while trying to fetch https://registry.npmjs.org/request: Integrity verification failed for sha512-OvNTHeHlQ0BJFyQnUquSMwp0FrkrHD5HpxXMr9Q/5/dPVA9ArajgORbw2bUQTWuQzvmb2KWT2Wm/PcOAIM50Wg== (/var/www/.npm/_cacache/content-v2/sha512/3a/f3/531de1e543404917242752ab92330a7416b92b1c3e47a715ccafd43fe7f74f540f40ada8e03916f0d9b5104d6b90cef99bd8a593d969bf3dc38020ce745a)
npm ERR! A complete log of this run can be found in:
npm ERR! /var/www/.npm/_logs/2022-02-02T07_13_17_947Z-debug.log
chown: cannot access 'node_modules': No such file or directory
Fin de l'installation
Je suis sous Jeedom 3.3.59 et EspEasy est en dernière version (2021-11-29 01:00:39).
Pouvez-vous s’il vous plait m’aider ?
Merci beaucoup d’avance…
Romain.