micro-ROS / micro-ROS/micro_ros_zephyr_module

Pip dependencies error while running Zephyr Emulator tutorial

Open
#132 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
92
Forks
56
PR merge metrics
No merged PRs in 30d

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.*

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
python
Domain
build-system
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.