-
Notifications
You must be signed in to change notification settings - Fork 95
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
First ROS2 debian release #124
Comments
I assigned this to myself for now since I'll do the first release into humble/rolling at our current state (it at least gets a mostly working openni2_camera driver out there) The timeline for the other tickets (and rgbd_launch) is really blocked on the upstream lazy subscriber stuff - and it will only work in Iron and later (those changes aren't going to make it into Humble, since it is a big API change in the ROS2 core) |
PRs required to get team/repo setup: |
Also, I've updated the first comment here to reflect that we won't be releasing openni2_launch in the first go-around (there is just too much upstream). This package also really doesn't support foxy anymore because there are too many API changes - so we'll be releasing only to Humble and Rolling (Foxy goes EOL in a little over 2 months anyways) |
Wondered how you could bloom-release the driver pkg without rgbd_launch. Then found in |
Yeah - that's also how our CI is working. I'm guessing it will be about 3-6 months before we can actually even start to port openni2_launch based on how much upstream stuff has to happen |
|
#128 should fix the humble build - not sure why our CI didn't detect that - something else must pull in pkgconfig |
New release with humble build fixes, and fixes for use_device_time not working: |
Humble build has succeeded:
The builds are still failing on RHEL - but that's because libopenni2 doesn't exist there - I think I disable bloom from putting those releases in |
ros2/ros_buildfarm_config#264 - to remove RHEL builds |
Ok - RHEL change is merged - I'm calling this complete |
humble
androlling
The text was updated successfully, but these errors were encountered: