Lors de l’installation des dépendance sur sonos 3, je rencontre ce message d’erreur :
+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_sonos3
+ echo 1
+ echo 2
+ sudo apt update
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://phoscon.de/apt/deconz buster InRelease
Hit:3 http://archive.raspberrypi.org/debian buster InRelease
Reading package lists...
Building dependency tree...
Reading state information...
158 packages can be upgraded. Run 'apt list --upgradable' to see them.
+ echo 3
+ sudo apt install -o Dpkg::Options::=--force-confdef -y libttspico-utils
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
Package libttspico-utils is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'libttspico-utils' has no installation candidate
+ echo 4
+ sudo systemctl restart apache2
Warning: The unit file, source configuration file or drop-ins of apache2.service changed on disk. Run 'systemctl daemon-reload' to reload units.
+ echo 5
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end sonos3
+ rm /tmp/jeedom_install_in_progress_sonos3
*******************End of package installation**************
probablement que ce paquet n’est plus dispo sous buster car cette version de debian est trop ancienne, c’est la fin pour buster et il faudra bien passer sous bullseye un jour
vous pouvez soit:
essayer de passer sous bullseye (debian11) mais vérifiez les plugins que vous avez avant pour être sur qu’ils sont compatibles
essayer d’installer manuellement le paquet manquant:
Un petit mot d’explication avec ce lien ne serait pas du luxe… perso je ne comprend pas ce que tu veux dire si tu sous-entends quelque chose.
et btw, c’est la feuille de compatibilité pour jeedom core, pas forcément pour tous les plugins tournant sous jeedom
et en l’occurrence, ici si une lib n’est plus dispo personne ne peut rien y faire, il faut avancer,
même s’il était écrit le contraire dans une doc, la seule conclusion serait qu’il faudra changer la doc
je ne sais pas garantir que cela va résoudre le problème, mais c’est probable.
effectivement pas d’image toute faite pour une install automatique mais il est possible d’installer « en ligne de commande »: https://doc.jeedom.com/fr_FR/installation/rpi
ne prenez pas la version « la plus récente » de raspi os (bookworm, debian12) mais bien la version bullseye; debian11
Bonjour
Je viens de migrer sous Bullseye et sous jeedom 4.4.
et il est impossible d’installer les dépendances. Le plugin fonctionne-t-il sous Bullseye ?
Va-t-il être mis à jour ?
D’autres personnes ont-ils le même problème ?
J’ai désinstallé le plugin puis je l’ai réinstallé, les dépendances ne veulent pas s’installer
voici le log
0000|+ echo '*******************Begin of package installation******************'
0001|*******************Begin of package installation******************
0002|+ touch /tmp/jeedom_install_in_progress_sonos3
0003|+ echo 1
0004|+ echo 2
0005|+ sudo killall apt apt-get unattended-upgr
0006|apt: no process found
0007|apt-get: no process found
0008|unattended-upgr: no process found
0009|+ sudo rm /var/lib/apt/lists/lock
0010|+ sudo rm /var/cache/apt/archives/lock
0011|rm: cannot remove '/var/cache/apt/archives/lock': No such file or directory
0012|+ sudo rm /var/lib/dpkg/lock /var/lib/dpkg/lock-frontend
0013|+ sudo sudo dpkg --configure -a --force-confdef
0014|+ sudo apt update
0015|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0016|Hit:1 http://deb.debian.org/debian bullseye InRelease
0017|Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
0018|Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
0019|Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
0020|Reading package lists...
0021|Building dependency tree...
0022|Reading state information...
0023|All packages are up to date.
0024|+ echo 3
0025|+ sudo apt install -o Dpkg::Options::=--force-confdef -y libav-tools
0026|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0027|Reading package lists...
0028|Building dependency tree...
0029|Reading state information...
0030|Package libav-tools is not available, but is referred to by another package.
0031|This may mean that the package is missing, has been obsoleted, or
0032|is only available from another source
0033|However the following packages replace it:
0034|ffmpeg
0035|E: Package 'libav-tools' has no installation candidate
0036|+ echo 4
0037|+ sudo apt install -o Dpkg::Options::=--force-confdef -y ffmpeg
0038|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0039|Reading package lists...
0040|Building dependency tree...
0041|Reading state information...
0042|ffmpeg is already the newest version (7:4.3.6-0+deb11u1).
0043|0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0044|+ echo 5
0045|+ sudo apt install -o Dpkg::Options::=--force-confdef -y libttspico-utils
0046|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0047|Reading package lists...
0048|Building dependency tree...
0049|Reading state information...
0050|Package libttspico-utils is not available, but is referred to by another package.
0051|This may mean that the package is missing, has been obsoleted, or
0052|is only available from another source
0053|E: Package 'libttspico-utils' has no installation candidate
0054|+ echo 6
0055|+ sudo apt install -o Dpkg::Options::=--force-confdef -y sox
0056|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0057|Reading package lists...
0058|Building dependency tree...
0059|Reading state information...
0060|sox is already the newest version (14.4.2+git20190427-2+deb11u2).
0061|0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0062|+ echo 7
0063|+ sudo apt install -o Dpkg::Options::=--force-confdef -y libsox-fmt-mp3
0064|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0065|Reading package lists...
0066|Building dependency tree...
0067|Reading state information...
0068|libsox-fmt-mp3 is already the newest version (14.4.2+git20190427-2+deb11u2).
0069|0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0070|+ echo 8
0071|+ sudo apt install -o Dpkg::Options::=--force-confdef -y smbclient
0072|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0073|Reading package lists...
0074|Building dependency tree...
0075|Reading state information...
0076|smbclient is already the newest version (2:4.13.13+dfsg-1~deb11u6).
0077|0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0078|+ echo 9
0079|+ sudo apt install -o Dpkg::Options::=--force-confdef -y php-mbstring
0080|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0081|Reading package lists...
0082|Building dependency tree...
0083|Reading state information...
0084|php-mbstring is already the newest version (2:7.4+76).
0085|0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0086|+ echo 10
0087|+ sudo apt install -o Dpkg::Options::=--force-confdef -y php-soap
0088|WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
0089|Reading package lists...
0090|Building dependency tree...
0091|Reading state information...
0092|php-soap is already the newest version (2:7.4+76).
0093|0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0094|+ echo 11
0095|+ sudo systemctl restart apache2
0096|+ echo 12
0097|+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end sonos3
0098|+ echo 13
0099|+ rm /tmp/jeedom_install_in_progress_sonos3
0100|+ echo '*******************End of package installation******************'
0101|*******************End of package installation******************
Petite précision.
J’ai installé le plugin sous jeedom V4.4.2 et BUSTER et il fonctionne. C’est quand je bascule jeedom sous bullseye 11.9 que les dépendances de s’installent plus
