Pip dependencies error while running Zephyr Emulator tutorial
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- build-system
Research direction
Start with firmware/zephyrproject/zephyr/scripts/requirements-doc.txt and reproduce the tutorial's create step in the ROS Humble dev container. Trace the pinned Sphinx and related package requirements, then verify that the create step completes without the reported pip dependency conflicts.
Written by the indexing model from the issue text.
Description
I am trying to run the Zephyr emulator tutorial in a VS code's dev container using a ros:humble image.
Steps to reproduce the issue
I cloned the Micro-ROS setup repo and launched the dev container which is running rosdep and building the initial workspace.
Expected behavior
Create step is effectively creating the firmware folder.
Actual behavior
The create step yields the following error (when running pip install --force-reinstall Sphinx==4.2.0 ):
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-tabs 3.2.0 requires docutils~=0.16.0, but you have docutils 0.17.1 which is incompatible.
sphinx-rtd-theme 0.5.2 requires docutils<0.17, but you have docutils 0.17.1 which is incompatible.
Additional information
It looks like the conflicts are coming from firmware/zephyrproject/zephyr/scripts/requirements-doc.txt where specified sphinx version is 3.*
- Dominant language
- C
- Stars
- 92
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from micro-ROS/micro_ros_zephyr_module
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
micro-ROS/micro_ros_zephyr_module#158 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
micro-ROS/micro_ros_zephyr_module#141 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in micro-ROS/micro_ros_zephyr_module
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dkfans/keeperfx#5415 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
void-linux/void-runit#141 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ARM-software/sysarch-acs#600 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day