Problème de dépendance kTwinkly

Bonjour, depuis la derniere MAJ ce plugin n’est plus fonctionnel.
A l’installation j’ai cette erreur

Requirement already satisfied: zipp>=0.5 in /usr/local/lib/python3.9/dist-packages (from importlib-metadata>=3.6.0->flask<2.3,>=1.1.1->mitmproxy) (3.19.2)
Requirement already satisfied: MarkupSafe>=2.0 in /usr/local/lib/python3.9/dist-packages (from Jinja2>=3.0->flask<2.3,>=1.1.1->mitmproxy) (2.1.5)
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
[notice] A new release of pip is available: 24.1.1 -> 24.1.2

Une idée?

Informations Jeedom

Core : 4.4.8.1 (V4-stable)
DNS Jeedom : oui

Plugin : Twinkly
Version : 2022-11-06 00:59:55 (stable)

Bonjour,

Aucune erreur là, tout va bien, tout est installé d’après le log.

Quel est le problème?

Et fournissez:

  • log complet ! Pas juste un extrait
  • capture écran page config du plugin
  • capture écran page santé jeedom

Ces éléments sont à fournir pour chaque demande.

Bonjour, voila toutes les infos manquantes:

Le Log

Progress file:  /tmp/jeedom/kTwinkly/dependencies
Sun Jul 21 17:40:23 CEST 2024
*
* Update package list
*
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
Reading package lists...
*
* Remove apt package for mitmproxy
Reading package lists...
Building dependency tree...
Reading state information...
Package 'mitmproxy' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
*
* Checking if default Python3 is version 3.7+
** Found Python 3.9.2
** Installing python3-setuptools
Reading package lists...
Building dependency tree...
Reading state information...
python3-dev is already the newest version (3.9.2-3).
python3-setuptools is already the newest version (52.0.0-4).
python3-wheel is already the newest version (0.34.2-1).
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Python 3.9.2
*
* Install mitmproxy module and dependencies on Python 3
Reading package lists...
Building dependency tree...
Reading state information...
libffi-dev is already the newest version (3.3-6).
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Requirement already satisfied: tornado in /usr/local/lib/python3.9/dist-packages (6.4.1)
Requirement already satisfied: mitmproxy in /usr/local/lib/python3.9/dist-packages (9.0.1)
Requirement already satisfied: asgiref<3.6,>=3.2.10 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (3.5.2)
Requirement already satisfied: Brotli<1.1,>=1.0 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (1.0.9)
Requirement already satisfied: certifi>=2019.9.11 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (2024.6.2)
Requirement already satisfied: cryptography<38.1,>=38.0 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (38.0.4)
Requirement already satisfied: flask<2.3,>=1.1.1 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (2.2.5)
Requirement already satisfied: h11<0.15,>=0.11 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (0.14.0)
Requirement already satisfied: h2<5,>=4.1 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (4.1.0)
Requirement already satisfied: hyperframe<7,>=6.0 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (6.0.1)
Requirement already satisfied: kaitaistruct<0.11,>=0.10 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (0.10)
Requirement already satisfied: ldap3<2.10,>=2.8 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (2.9.1)
Requirement already satisfied: mitmproxy-wireguard<0.2,>=0.1.6 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (0.1.23)
Requirement already satisfied: msgpack<1.1.0,>=1.0.0 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (1.0.8)
Requirement already satisfied: passlib<1.8,>=1.6.5 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (1.7.4)
Requirement already satisfied: protobuf<5,>=3.14 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (4.25.3)
Requirement already satisfied: pyOpenSSL<22.2,>=22.1 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (22.1.0)
Requirement already satisfied: pyparsing<3.1,>=2.4.2 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (3.0.9)
Requirement already satisfied: pyperclip<1.9,>=1.6.0 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (1.8.2)
Requirement already satisfied: ruamel.yaml<0.18,>=0.16 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (0.17.40)
Requirement already satisfied: sortedcontainers<2.5,>=2.3 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (2.4.0)
Requirement already satisfied: urwid<2.2,>=2.1.1 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (2.1.2)
Requirement already satisfied: wsproto<1.3,>=1.0 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (1.2.0)
Requirement already satisfied: publicsuffix2<3,>=2.20190812 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (2.20191221)
Requirement already satisfied: zstandard<0.20,>=0.11 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (0.19.0)
Requirement already satisfied: typing-extensions<4.5,>=4.3 in /usr/local/lib/python3.9/dist-packages (from mitmproxy) (4.4.0)
Requirement already satisfied: cffi>=1.12 in /usr/local/lib/python3.9/dist-packages (from cryptography<38.1,>=38.0->mitmproxy) (1.16.0)
Requirement already satisfied: Werkzeug>=2.2.2 in /usr/local/lib/python3.9/dist-packages (from flask<2.3,>=1.1.1->mitmproxy) (3.0.3)
Requirement already satisfied: Jinja2>=3.0 in /usr/local/lib/python3.9/dist-packages (from flask<2.3,>=1.1.1->mitmproxy) (3.1.4)
Requirement already satisfied: itsdangerous>=2.0 in /usr/local/lib/python3.9/dist-packages (from flask<2.3,>=1.1.1->mitmproxy) (2.2.0)
Requirement already satisfied: click>=8.0 in /usr/local/lib/python3.9/dist-packages (from flask<2.3,>=1.1.1->mitmproxy) (8.1.7)
Requirement already satisfied: importlib-metadata>=3.6.0 in /usr/local/lib/python3.9/dist-packages (from flask<2.3,>=1.1.1->mitmproxy) (7.2.1)
Requirement already satisfied: hpack<5,>=4.0 in /usr/local/lib/python3.9/dist-packages (from h2<5,>=4.1->mitmproxy) (4.0.0)
Requirement already satisfied: pyasn1>=0.4.6 in /usr/local/lib/python3.9/dist-packages (from ldap3<2.10,>=2.8->mitmproxy) (0.6.0)
Requirement already satisfied: ruamel.yaml.clib>=0.2.7 in /usr/local/lib/python3.9/dist-packages (from ruamel.yaml<0.18,>=0.16->mitmproxy) (0.2.8)
Requirement already satisfied: pycparser in /usr/local/lib/python3.9/dist-packages (from cffi>=1.12->cryptography<38.1,>=38.0->mitmproxy) (2.22)
Requirement already satisfied: zipp>=0.5 in /usr/local/lib/python3.9/dist-packages (from importlib-metadata>=3.6.0->flask<2.3,>=1.1.1->mitmproxy) (3.19.2)
Requirement already satisfied: MarkupSafe>=2.0 in /usr/local/lib/python3.9/dist-packages (from Jinja2>=3.0->flask<2.3,>=1.1.1->mitmproxy) (2.1.5)
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable.It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
[notice] A new release of pip is available: 24.1.1 -> 24.1.2
[notice] To update, run: python3 -m pip install --upgrade pip
Sun Jul 21 17:40:25 CEST 2024`


Avant la mise a jour en jeedom 4.4 tous était fonctionnelle, je suis repartis sur une installation neuve avec un import de la base.
L’installation se lance et se fini mais le plugin reste comme si les dépendances n’était pas installé…

Bonjour

Comment êtes-vous passé de debian 10 à 11?
Le fait d’avoir du python 2.x sur une debian 11 est étonnant.

Antoine

je sui passe par l’iso officielle https://images.jeedom.com/x86-64/.

Puis mise à jour en jeedom 4.4

Donc vous l’avez installé par la suite?

Antoine

Non je ne suis passe que par le systeme jeedom je n’ai rien fait manuellement.
Si il s’est installer cela est par le systeme.

Le problème est celui-ci: Problème installation dépendances avec l'erreur: "Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'" - #30 par Mips que j’ai fixé dans le core mais ce plugin n’utilise pas le système de dépendances du core donc il doit être corrigé par son auteur.

On ne pourra rien faire de plus.

Pour dépanner vous pouvez appliquer le contournement donné dans le post ci-dessus mais n’installez plus les dépendances ensuite.


La présence de python2.7 n’est pas un problème en soit. Selon moi aucune action à prendre à ce sujet.

Le code est sur Github

Donc il est possible de faire un PR, mais je ne sais pas si @kimagure maintient toujours son plugin.

PR fait:

mais je vois pas mal de bug à corriger à coté, je n’ai pas touché n’ayant pas le plugin

1 « J'aime »

Bonjour

Désolé, je n’utilise plus Jeedom et je n’ai plus le temps de maintenir le plugin.

Dans ma roadmap, je voulais découpler le proxy de capture du plugin lui-meme pour éviter toutes ces dépendances inutiles, puisqu’on ne capture pas forcément de nouvelles animation tous les jours. Si on sort le proxy, le plugin n’a plus aucune dépendance, il ne fait que des appels http.

Si quelqu’un veut reprendre le code, pas de souci.

J’ai fusionné le PR de Mips dans la branche beta du github.

K.

2 « J'aime »