-
Notifications
You must be signed in to change notification settings - Fork 406
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
Use upstream repo, not fmauch/universal_robot #84
Comments
Yes. |
Now that we have an open issue clearly covering this: There is a PR going on changing a lot in generating the robot descriptions. We plan to merge this in first, so the calibration stuff will be generated on top of that. The current PR of my fork is therefore currently on hold. |
@fmauch @gavanderhoorn I guess this is also related to ros-industrial/universal_robot#448 The Or has this been covered in ros-industrial/universal_robot#495? |
I had hoped the I can assure you once things have been merged and released we will be vocal about it. Then the readmes can be updated. |
I am interested in seeing this getting cleaned up. Anyway we can make progress on this? I am also hoping we can get a proper package built and deployed for Melodic. |
This seems like is has been resolved long ago... |
Currently the README build instructions ask us to clone fmauch/universal_robot, which is a branch in a fork of a fork. I'd like to submit a fix to this repo but it would be best if I could submit that fix to the upstream https://github.com/ros-industrial/universal_robot.
Are there efforts to get these changes merged back into the original ROS-Industrial repo? @gavanderhoorn ?
Side note, the fix I'd like to make:
The text was updated successfully, but these errors were encountered: