-
Notifications
You must be signed in to change notification settings - Fork 49
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
bloom release #38
Comments
http://wiki.ros.org/regression_tests#How_do_I_setup_my_system_to_run_a_prerelease.3F
There isn't any package named that in 20.04 noetic (or do I need to add a repo?), so skip pre-release- or maybe it is in pip? |
👎 |
I've forgotten how much I dislike interactive shell scripts for processes like this- if the configuration requires more than a handful of command line parameters it should use a config file instead, and process that instead of constantly stopping to ask the user questions. |
Try making this modification
Actually the solution is to use this:
But can't do that with the override
|
|
https://github.com/lucasw/rviz_camera_stream/releases/tag/1.0.0/info/refs
Try https://github.com/lucasw/rviz_camera_stream.git instead? |
|
-> http://wiki.ros.org/bloom/Tutorials/GithubManualAuthorization#Re-route_https_through_ssh Re-running the bloom command is easier now, it remembers all the above settings It still asks for an access token Do a manual PR |
Forgot to add a LICENSE, bumping to 1.0.1 Instead of bloom just do whatever it did manually in the release repo https://github.com/lucasw/rviz_camera_stream-release No there's too much there, just run bloom again
|
Opened manual PR at ros/rosdistro#30895 It failed like this:
Aren't I just releasing into noetic? then whay is melodic running above? Also I do have that tag: https://github.com/lucasw/rviz_camera_stream/releases/tag/1.0.1 https://github.com/lucasw/rviz_camera_stream-release/releases/tag/upstream%2F1.0.1 The tag must be a branch? ros/rosdistro#20286 In which repo, the |
http://wiki.ros.org/bloom/Tutorials/FirstTimeRelease
The text was updated successfully, but these errors were encountered: