Je viens de migrer ma smart en Atlas et les dépendances de ce plugin ne s’installent plus
Voici les les log des dépendances
* Installation des dépendances *
********************************************************
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://security.debian.org buster/updates InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 http://deb.debian.org/debian buster-backports InRelease
Hit:5 https://deb.nodesource.com/node_16.x buster InRelease
Hit:6 http://armbian.hosthatch.com/apt buster InRelease
Reading package lists...
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
Requirement already satisfied: setuptools in /usr/local/lib/python3.7/dist-packages (65.5.0)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
Requirement already satisfied: pyudev in /usr/lib/python3/dist-packages (0.21.0)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Requirement already satisfied: pyserial in /usr/lib/python3/dist-packages (3.4)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Requirement already satisfied: requests in /usr/local/lib/python3.7/dist-packages (2.28.1)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.7/dist-packages (from requests) (2022.9.24)
Requirement already satisfied: charset-normalizer<3,>=2 in /usr/local/lib/python3.7/dist-packages (from requests) (2.1.1)
Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.7/dist-packages (from requests) (3.4)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/local/lib/python3.7/dist-packages (from requests) (1.26.12)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Collecting pybluez
Using cached PyBluez-0.23.tar.gz (97 kB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'error'
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [1 lines of output]
error in PyBluez setup command: use_2to3 is invalid.
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
Requirement already satisfied: pillow in /usr/local/lib/python3.7/dist-packages (9.3.0)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Requirement already satisfied: numpy in /usr/local/lib/python3.7/dist-packages (1.21.6)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Collecting bluepy
Using cached bluepy-1.3.0.tar.gz (217 kB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'done'
Installing collected packages: bluepy
DEPRECATION: bluepy is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
Running setup.py install for bluepy: started
Running setup.py install for bluepy: finished with status 'done'
Successfully installed bluepy
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Cloning into 'bluepy'...
running build
running build_py
creating build
creating build/lib
creating build/lib/bluepy
copying bluepy/thingy52.py -> build/lib/bluepy
copying bluepy/sensortag.py -> build/lib/bluepy
copying bluepy/scanner.py -> build/lib/bluepy
copying bluepy/scan_fuzz.py -> build/lib/bluepy
copying bluepy/get_services.py -> build/lib/bluepy
copying bluepy/btle.py -> build/lib/bluepy
copying bluepy/blescan.py -> build/lib/bluepy
copying bluepy/__init__.py -> build/lib/bluepy
copying bluepy/uuids.json -> build/lib/bluepy
copying bluepy/bluez-src.tgz -> build/lib/bluepy
copying bluepy/bluepy-helper.c -> build/lib/bluepy
copying bluepy/Makefile -> build/lib/bluepy
/usr/local/lib/python3.7/dist-packages/setuptools/dist.py:774: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead
% (opt, underscore_opt)
running install
Working dir is /tmp/bluepy
execute make -C ./bluepy clean
execute make -C bluepy -j1
running build
running build_py
copying bluepy/bluepy-helper -> build/lib/bluepy
running install_lib
copying build/lib/bluepy/bluepy-helper -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/Makefile -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/bluepy-helper.c -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/bluez-src.tgz -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/uuids.json -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/__init__.py -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/blescan.py -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/btle.py -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/get_services.py -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/scan_fuzz.py -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/scanner.py -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/sensortag.py -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/thingy52.py -> /usr/lib/python3.7/site-packages/bluepy
byte-compiling /usr/lib/python3.7/site-packages/bluepy/__init__.py to __init__.cpython-37.pyc
byte-compiling /usr/lib/python3.7/site-packages/bluepy/blescan.py to blescan.cpython-37.pyc
byte-compiling /usr/lib/python3.7/site-packages/bluepy/btle.py to btle.cpython-37.pyc
byte-compiling /usr/lib/python3.7/site-packages/bluepy/get_services.py to get_services.cpython-37.pyc
byte-compiling /usr/lib/python3.7/site-packages/bluepy/scan_fuzz.py to scan_fuzz.cpython-37.pyc
byte-compiling /usr/lib/python3.7/site-packages/bluepy/scanner.py to scanner.cpython-37.pyc
byte-compiling /usr/lib/python3.7/site-packages/bluepy/sensortag.py to sensortag.cpython-37.pyc
byte-compiling /usr/lib/python3.7/site-packages/bluepy/thingy52.py to thingy52.cpython-37.pyc
running install_egg_info
running egg_info
creating bluepy.egg-info
writing bluepy.egg-info/PKG-INFO
writing dependency_links to bluepy.egg-info/dependency_links.txt
writing entry points to bluepy.egg-info/entry_points.txt
writing top-level names to bluepy.egg-info/top_level.txt
writing manifest file 'bluepy.egg-info/SOURCES.txt'
reading manifest file 'bluepy.egg-info/SOURCES.txt'
adding license file 'LICENSE.txt'
writing manifest file 'bluepy.egg-info/SOURCES.txt'
removing '/usr/lib/python3.7/site-packages/bluepy-1.1.4-py3.7.egg-info' (and everything under it)
Copying bluepy.egg-info to /usr/lib/python3.7/site-packages/bluepy-1.1.4-py3.7.egg-info
running install_scripts
Installing blescan script to /usr/bin
Installing sensortag script to /usr/bin
Installing thingy52 script to /usr/bin
/usr/local/lib/python3.7/dist-packages/setuptools/dist.py:774: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead
% (opt, underscore_opt)
/usr/local/lib/python3.7/dist-packages/setuptools/command/install.py:37: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
setuptools.SetuptoolsDeprecationWarning,
Requirement already satisfied: cryptography in /usr/local/lib/python3.7/dist-packages (38.0.3)
Requirement already satisfied: cffi>=1.12 in /usr/local/lib/python3.7/dist-packages (from cryptography) (1.15.1)
Requirement already satisfied: pycparser in /usr/local/lib/python3.7/dist-packages (from cffi>=1.12->cryptography) (2.21)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Collecting pycrypto
Using cached pycrypto-2.6.1.tar.gz (446 kB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'done'
Installing collected packages: pycrypto
DEPRECATION: pycrypto is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
Running setup.py install for pycrypto: started
Running setup.py install for pycrypto: finished with status 'done'
Successfully installed pycrypto
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
********************************************************
* Installation terminée *
********************************************************
Alors j’ai exécuté la commande , dsl je n’avais pas vu/compris le log
le nouveau log est differents
* Installation des dépendances *
********************************************************
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian buster-updates InRelease
Hit:3 http://deb.debian.org/debian buster-backports InRelease
Hit:4 http://security.debian.org buster/updates InRelease
Hit:5 https://deb.nodesource.com/node_16.x buster InRelease
Hit:6 http://armbian.hosthatch.com/apt buster InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
libatlas-base-dev is already the newest version (3.10.3-8).
build-essential is already the newest version (12.6).
libffi-dev is already the newest version (3.2.1-9).
libopenjp2-7 is already the newest version (2.3.0-2+deb10u2).
libssl-dev is already the newest version (1.1.1n-0+deb10u3).
python3-serial is already the newest version (3.4-4).
python3-setuptools is already the newest version (40.8.0-1).
python3-dev is already the newest version (3.7.3-1).
python3-pyudev is already the newest version (0.21.0-1).
python3-requests is already the newest version (2.21.0-1).
libtiff5 is already the newest version (4.1.0+git191117-2~deb10u4).
rfkill is already the newest version (2.33.1-0.1).
bluetooth is already the newest version (5.50-1.2~deb10u3).
libbluetooth-dev is already the newest version (5.50-1.2~deb10u3).
0 upgraded, 0 newly installed, 0 to remove and 164 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
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, 0 newly installed, 3 reinstalled, 0 to remove and 164 not upgraded.
Need to get 0 B/1,191 kB of archives.
After this operation, 0 B of additional disk space will be used.
(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 ... 62281 files and directories currently installed.)
Preparing to unpack .../python3_3.7.3-1_arm64.deb ...
running python pre-rtupdate hooks for python3.7...
Unpacking python3 (3.7.3-1) over (3.7.3-1) ...
Preparing to unpack .../bluez_5.50-1.2~deb10u3_arm64.deb ...
Unpacking bluez (5.50-1.2~deb10u3) over (5.50-1.2~deb10u3) ...
Preparing to unpack .../python3-pip_18.1-5_all.deb ...
Unpacking python3-pip (18.1-5) over (18.1-5) ...
Setting up python3 (3.7.3-1) ...
running python rtupdate hooks for python3.7...
running python post-rtupdate hooks for python3.7...
Setting up bluez (5.50-1.2~deb10u3) ...
Setting up python3-pip (18.1-5) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for dbus (1.12.20-0+deb10u1) ...
Processing triggers for systemd (241-7~deb10u8) ...
Requirement already satisfied: setuptools in /usr/local/lib/python3.7/dist-packages (65.5.1)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Reading package lists...
Building dependency tree...
Reading state information...
git is already the newest version (1:2.20.1-2+deb10u4).
libglib2.0-dev is already the newest version (2.58.3-2+deb10u4).
0 upgraded, 0 newly installed, 0 to remove and 164 not upgraded.
Requirement already satisfied: pyudev in /usr/lib/python3/dist-packages (0.21.0)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Requirement already satisfied: pyserial in /usr/lib/python3/dist-packages (3.4)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Requirement already satisfied: requests in /usr/local/lib/python3.7/dist-packages (2.28.1)
Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.7/dist-packages (from requests) (3.4)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in /usr/local/lib/python3.7/dist-packages (from requests) (1.26.12)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.7/dist-packages (from requests) (2022.9.24)
Requirement already satisfied: charset-normalizer<3,>=2 in /usr/local/lib/python3.7/dist-packages (from requests) (2.1.1)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Collecting pybluez
Using cached PyBluez-0.23.tar.gz (97 kB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'error'
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [1 lines of output]
error in PyBluez setup command: use_2to3 is invalid.
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
Requirement already satisfied: pillow in /usr/local/lib/python3.7/dist-packages (9.3.0)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Requirement already satisfied: numpy in /usr/local/lib/python3.7/dist-packages (1.21.6)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Collecting bluepy
Using cached bluepy-1.3.0.tar.gz (217 kB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'done'
Installing collected packages: bluepy
DEPRECATION: bluepy is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
Running setup.py install for bluepy: started
Running setup.py install for bluepy: finished with status 'done'
Successfully installed bluepy
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Cloning into 'bluepy'...
running build
running build_py
creating build
creating build/lib
creating build/lib/bluepy
copying bluepy/thingy52.py -> build/lib/bluepy
copying bluepy/sensortag.py -> build/lib/bluepy
copying bluepy/scanner.py -> build/lib/bluepy
copying bluepy/scan_fuzz.py -> build/lib/bluepy
copying bluepy/get_services.py -> build/lib/bluepy
copying bluepy/btle.py -> build/lib/bluepy
copying bluepy/blescan.py -> build/lib/bluepy
copying bluepy/__init__.py -> build/lib/bluepy
copying bluepy/uuids.json -> build/lib/bluepy
copying bluepy/bluez-src.tgz -> build/lib/bluepy
copying bluepy/bluepy-helper.c -> build/lib/bluepy
copying bluepy/Makefile -> build/lib/bluepy
/usr/local/lib/python3.7/dist-packages/setuptools/dist.py:774: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead
% (opt, underscore_opt)
running install
Working dir is /tmp/bluepy
execute make -C ./bluepy clean
execute make -C bluepy -j1
running build
running build_py
copying bluepy/bluepy-helper -> build/lib/bluepy
running install_lib
copying build/lib/bluepy/bluepy-helper -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/Makefile -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/bluepy-helper.c -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/bluez-src.tgz -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/uuids.json -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/__init__.py -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/blescan.py -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/btle.py -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/get_services.py -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/scan_fuzz.py -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/scanner.py -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/sensortag.py -> /usr/lib/python3.7/site-packages/bluepy
copying build/lib/bluepy/thingy52.py -> /usr/lib/python3.7/site-packages/bluepy
byte-compiling /usr/lib/python3.7/site-packages/bluepy/__init__.py to __init__.cpython-37.pyc
byte-compiling /usr/lib/python3.7/site-packages/bluepy/blescan.py to blescan.cpython-37.pyc
byte-compiling /usr/lib/python3.7/site-packages/bluepy/btle.py to btle.cpython-37.pyc
byte-compiling /usr/lib/python3.7/site-packages/bluepy/get_services.py to get_services.cpython-37.pyc
byte-compiling /usr/lib/python3.7/site-packages/bluepy/scan_fuzz.py to scan_fuzz.cpython-37.pyc
byte-compiling /usr/lib/python3.7/site-packages/bluepy/scanner.py to scanner.cpython-37.pyc
byte-compiling /usr/lib/python3.7/site-packages/bluepy/sensortag.py to sensortag.cpython-37.pyc
byte-compiling /usr/lib/python3.7/site-packages/bluepy/thingy52.py to thingy52.cpython-37.pyc
running install_egg_info
running egg_info
creating bluepy.egg-info
writing bluepy.egg-info/PKG-INFO
writing dependency_links to bluepy.egg-info/dependency_links.txt
writing entry points to bluepy.egg-info/entry_points.txt
writing top-level names to bluepy.egg-info/top_level.txt
writing manifest file 'bluepy.egg-info/SOURCES.txt'
reading manifest file 'bluepy.egg-info/SOURCES.txt'
adding license file 'LICENSE.txt'
writing manifest file 'bluepy.egg-info/SOURCES.txt'
removing '/usr/lib/python3.7/site-packages/bluepy-1.1.4-py3.7.egg-info' (and everything under it)
Copying bluepy.egg-info to /usr/lib/python3.7/site-packages/bluepy-1.1.4-py3.7.egg-info
running install_scripts
Installing blescan script to /usr/bin
Installing sensortag script to /usr/bin
Installing thingy52 script to /usr/bin
/usr/local/lib/python3.7/dist-packages/setuptools/dist.py:774: UserWarning: Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead
% (opt, underscore_opt)
/usr/local/lib/python3.7/dist-packages/setuptools/command/install.py:37: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
setuptools.SetuptoolsDeprecationWarning,
Requirement already satisfied: cryptography in /usr/local/lib/python3.7/dist-packages (38.0.3)
Requirement already satisfied: cffi>=1.12 in /usr/local/lib/python3.7/dist-packages (from cryptography) (1.15.1)
Requirement already satisfied: pycparser in /usr/local/lib/python3.7/dist-packages (from cffi>=1.12->cryptography) (2.21)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Collecting pycrypto
Using cached pycrypto-2.6.1.tar.gz (446 kB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'done'
Installing collected packages: pycrypto
DEPRECATION: pycrypto is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
Running setup.py install for pycrypto: started
Running setup.py install for pycrypto: finished with status 'done'
Successfully installed pycrypto
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
********************************************************
* Installation terminée *
********************************************************
Dans les autres post il parle de version , de mon coté ca donne ca
Par contre je n’arrive pas a voir si c’est la bonne piste pour moi
et les manips exacte a faire
