Il m’est impossible d’installer les dépendances pour Homebridge
J’ai essayé tout ce que j’ai trouvé sur le forum
Installation sur RPI3 Raspian Jeedom 3.3.39
Ci dessous le log
--0%
Lancement de l'installation/mise à jour des dépendances homebridge
Vérification si la source repo.jeedom.com existe (bug lors de l'installation de node 6 si c'est le cas)
--5%
Hit:1 http://mirrordirector.raspbian.org/raspbian stretch InRelease
Get:2 http://archive.raspberrypi.org/debian stretch InRelease [25.4 kB]
Fetched 25.4 kB in 3s (7272 B/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
avahi-daemon is already the newest version (0.6.32-2).
avahi-discover is already the newest version (0.6.32-2).
avahi-utils is already the newest version (0.6.32-2).
libavahi-compat-libdnssd-dev is already the newest version (0.6.32-2).
libnss-mdns is already the newest version (0.10-8).
0 upgraded, 0 newly installed, 0 to remove and 412 not upgraded.
--10%
Version actuelle : v8.11.1
Ok, version suffisante
--40%
Installation de node-gyp...
sudo: npm: command not found
Installation de request...
sudo: npm: command not found
--50%
/var/www/html/plugins/homebridge/core/class/../../resources/install_homebridge.sh: line 137: npm: command not found
--60%
Installation de Homebridge...
sudo: npm: command not found
--70%
Installation de Homebridge-Jeedom...
Sur la branche master
sudo: npm: command not found
Installation de Homebridge-Camera-FFMPEG...
sudo: npm: command not found
--80%
--90%
Désactivation de avahi-daemon au démarrage...(il démarrera avec le daemon (on contourne le bug de la Smart du 1 jan 1970))
Installation Homebridge OK
--100%
--0%
Lancement de l'installation/mise à jour des dépendances homebridge
Vérification si la source repo.jeedom.com existe (bug lors de l'installation de node 6 si c'est le cas)
--5%
Get:1 http://archive.raspberrypi.org/debian stretch InRelease [25.4 kB]
Hit:2 http://mirrordirector.raspbian.org/raspbian stretch InRelease
Fetched 25.4 kB in 10s (2403 B/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
avahi-daemon is already the newest version (0.6.32-2).
avahi-discover is already the newest version (0.6.32-2).
avahi-utils is already the newest version (0.6.32-2).
libavahi-compat-libdnssd-dev is already the newest version (0.6.32-2).
libnss-mdns is already the newest version (0.10-8).
0 upgraded, 0 newly installed, 0 to remove and 412 not upgraded.
--10%
/var/www/html/plugins/homebridge/core/class/../../resources/install_homebridge.sh: line 55: nodejs: command not found
Version actuelle :
--20%
KO, version obsolète à upgrader
Suppression du Nodejs existant et installation du paquet recommandé
sudo: npm: command not found
sudo: npm: command not found
sudo: npm: command not found
sudo: npm: command not found
sudo: npm: command not found
/var/www/html/plugins/homebridge/core/class/../../resources/install_homebridge.sh: line 74: npm: command not found
sudo: npm: command not found
Reading package lists...
Building dependency tree...
Reading state information...
Package 'npm' is not installed, so not removed
Package 'nodejs' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 412 not upgraded.
--30%
Utilisation du dépot officiel
================================================================================
================================================================================
DEPRECATION WARNING
Node.js 5.x is no longer actively supported!
You will not receive security or critical stability updates for this version.
You should migrate to a supported version of Node.js as soon as possible.
Use the installation script that corresponds to the version of Node.js you
wish to install. e.g.
* https://deb.nodesource.com/setup_10.x — Node.js 10 LTS "Dubnium" (recommended)
* https://deb.nodesource.com/setup_12.x — Node.js 12 LTS "Erbium"
Please see https://github.com/nodejs/Release for details about which
version may be appropriate for you.
The NodeSource Node.js distributions repository contains
information both about supported versions of Node.js and supported Linux
distributions. To learn more about usage, see the repository:
https://github.com/nodesource/distributions
================================================================================
================================================================================
Continuing in 20 seconds ...
## Installing the NodeSource Node.js 5.x repo...
## Populating apt-get cache...
+ apt-get update
Get:1 http://archive.raspberrypi.org/debian stretch InRelease [25.4 kB]
Hit:2 http://mirrordirector.raspbian.org/raspbian stretch InRelease
Fetched 25.4 kB in 0s (26.2 kB/s)
Reading package lists...
## Confirming "stretch" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_5.x/dists/stretch/Release'
## Your distribution, identified as "stretch", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support
Warning: apt-key output should not be parsed (stdout is not a terminal)
Warning: 'apt-key update' is deprecated and should not be used anymore!
gpg: key 9165938D90FDDD2E: "Mike Thompson (Raspberry Pi Debian armhf ARMv6+VFP) <mpthompson@gmail.com>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
W: Removed keys keyring '/usr/share/keyrings/raspbian-archive-removed-keys.gpg' missing or not readable
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
libc-ares2 libhttp-parser2.8 libuv1 nodejs-doc
The following NEW packages will be installed:
libc-ares2 libhttp-parser2.8 libuv1 nodejs nodejs-doc
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:
0 upgraded, 5 newly installed, 0 to remove and 412 not upgraded.
Need to get 0 B/5087 kB of archives.
After this operation, 22.2 MB of additional disk space will be used.
Selecting previously unselected package libc-ares2:armhf.
(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 ... 132460 files and directories currently installed.)
Preparing to unpack .../libc-ares2_1.14.0-1~bpo9+1_armhf.deb ...
Unpacking libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Selecting previously unselected package libhttp-parser2.8:armhf.
Preparing to unpack .../libhttp-parser2.8_2.8.1-1~bpo9+1_armhf.deb ...
Unpacking libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Selecting previously unselected package libuv1:armhf.
Preparing to unpack .../libuv1_1.18.0-3~bpo9+1_armhf.deb ...
Unpacking libuv1:armhf (1.18.0-3~bpo9+1) ...
Selecting previously unselected package nodejs.
Preparing to unpack .../nodejs_8.11.1~dfsg-2~bpo9+1_armhf.deb ...
Unpacking nodejs (8.11.1~dfsg-2~bpo9+1) ...
Selecting previously unselected package nodejs-doc.
Preparing to unpack .../nodejs-doc_8.11.1~dfsg-2~bpo9+1_all.deb ...
Unpacking nodejs-doc (8.11.1~dfsg-2~bpo9+1) ...
Setting up nodejs-doc (8.11.1~dfsg-2~bpo9+1) ...
Setting up libuv1:armhf (1.18.0-3~bpo9+1) ...
Processing triggers for libc-bin (2.24-11+deb9u1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up libc-ares2:armhf (1.14.0-1~bpo9+1) ...
Setting up libhttp-parser2.8:armhf (2.8.1-1~bpo9+1) ...
Setting up nodejs (8.11.1~dfsg-2~bpo9+1) ...
update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode
Processing triggers for libc-bin (2.24-11+deb9u1) ...
Version actuelle : v8.11.1
--40%
Installation de node-gyp...
sudo: npm: command not found
Installation de request...
sudo: npm: command not found
--50%
/var/www/html/plugins/homebridge/core/class/../../resources/install_homebridge.sh: line 137: npm: command not found
--60%
Installation de Homebridge...
sudo: npm: command not found
--70%
Installation de Homebridge-Jeedom...
Sur la branche master
sudo: npm: command not found
Installation de Homebridge-Camera-FFMPEG...
sudo: npm: command not found
--80%
--90%
Désactivation de avahi-daemon au démarrage...(il démarrera avec le daemon (on contourne le bug de la Smart du 1 jan 1970))
Installation Homebridge OK
--100%
Je confirme, tu as essayé d’entourlouper en prenant la version github sur le repo de jeedom. Aucun support sur cette version évidemment elle date de 2 ans !!