-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing dependency on ament_cmake_flake8
?
#198
Comments
130s
added a commit
to 130s/rosidl_python
that referenced
this issue
Jul 14, 2023
In ver 0.19.0, |
130s
added a commit
to 130s/rosidl_python
that referenced
this issue
Jul 14, 2023
ros2#198) Signed-off-by: Isaac Saito <130s@2000.jukuin.keio.ac.jp>
130s
added a commit
to 130s/executive_smach
that referenced
this issue
Jul 14, 2023
130s
added a commit
to 130s/rosidl_python
that referenced
this issue
Jul 14, 2023
ros2#198) Signed-off-by: Isaac Saito <130s@2000.jukuin.keio.ac.jp>
130s
added a commit
to 130s/executive_smach
that referenced
this issue
Jul 14, 2023
130s
added a commit
to 130s/executive_smach
that referenced
this issue
Jul 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue report
Required Info:
Steps to reproduce issue
Buildfarm output https://build.ros2.org/job/Rpr__smach__ubuntu_jammy_amd64/2/console for ros/executive_smach#112 where a dependency on
ament_cmake_flake8
is removed in a downstream package (smach_msgs
) so that none of the packages in the repo in the PR depends on nor callament_cmake_flake8
any more.(I haven't figured out exactly what command was called when the reported error occured. My guess is either some sort of `rosidl` command was called, or `colcon build`
Expected behavior
In a downstream interface package, no error during
cmake
regardingament_cmake_flake8Config.cmake / ament_cmake_flake8-config.cmake
should be seen while building rosidl package, even when the downstream interface package does NOT explicitly depend onament_cmake_flake8
.Actual behavior
The error posted in "Steps to reproduce issue" section occurs.
The text was updated successfully, but these errors were encountered: