-
Notifications
You must be signed in to change notification settings - Fork 227
fix "ros2 invalid choice: 'launch'" by rosdep install #293
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
Conversation
humble had the same issue. Do i make a seperate pr for that or is there some github magic I'm not aware of? |
Normally, we trigger a backport manually after it is merged to the master branch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Never had a installation before without that being installed..
@Mergifyio backport humble |
ye I'm working on the docker file and it was saying ros2 doesn't have a launch command my brain went ?????? |
✅ Backports have been created
|
(cherry picked from commit eb60429)
While trying to add dockerfiles for this repo it was throwing this:
Solution inspired by:
https://github.com/ros-controls/gz_ros2_control/blob/master/gz_ros2_control_demos/package.xml#L36
the other launch deps are not needed since they are already listed for ros2launch.