micro-ROS / micro-ROS/micro_ros_setup
Dependency Conflict in micro-ROS Zephyr Setup Due to docutils Version Incompatibility
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Shell
- Estrellas
- 509
- Forks
- 183
- Merge medio
- 22 h 26 min
- PR fusionados (30 d)
- 7
Descripción
Dependency Conflict in micro-ROS Zephyr Setup Due to docutils Version Incompatibility
-
Hardware description: N/A (not hardware specific)
-
RTOS: Zephyr
-
Installation type:
micro_ros_setup -
Version or commit hash: a146e83
-
Python version: Python 3.10.12
-
OS: Ubuntu 22.04.5 LTS
Steps to reproduce the issue
- Follow the micro-ROS Zephyr setup instructions.
- Run the following command to create a firmware workspace:
ros2 run micro_ros_setup create_firmware_ws.sh zephyr - The script fails with a
docutilsversion conflict.
Expected behavior
The firmware workspace should be created without any dependency conflicts.
Actual behavior
The script fails with the following error due to an incompatibility between sphinx-rtd-theme and the installed version of docutils:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
sphinx-rtd-theme 0.5.2 requires docutils<0.17, but you have docutils 0.17.1 which is incompatible.
Additional information
I was able to resolve the issue by modifying the create.sh file in src/micro_ros_setup/config/zephyr/generic/ at line 70:
pip install --force-reinstall docutils==0.16 Sphinx==4.2.0
This forces the installation of a compatible version of docutils and prevents pip from installing docutils 0.17.1. To fix the issue permanently, I suggest adding this change to the official create.sh script to ensure compatibility with sphinx-rtd-theme 0.5.2.
I tested this issue both in my local environment (Ubuntu 22.04.5 LTS) and in the official Humble Docker container. The issue was reproducible in both setups.
The full logs are available if needed, but they are quite lengthy.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comienza con src/micro_ros_setup/config/zephyr/generic/create.sh alrededor de la línea 70 y revisa la instalación de dependencias utilizada por create_firmware_ws.sh zephyr. Reproduce el problema con ros2 run micro_ros_setup create_firmware_ws.sh zephyr en el contenedor Docker de Humble o en Ubuntu 22.04. Se considera terminado cuando el workspace de firmware se crea sin el conflicto entre docutils y sphinx-rtd-theme.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- python, shell
- Área
- build-system, tooling
- Tipo de issue
- Error
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Estado de actividad
- Estancado
- Claridad
- Bien especificado
- Aptitud para principiantes
- 45/100