-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Bump libpcl* to 1.14 on Ubuntu Noble #40834
Conversation
Signed-off-by: Shane Loretz <[email protected]>
Signed-off-by: Chris Lalancette <[email protected]>
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.
Yep, this looks good to me. I ended up adding a few more missing keys that we hadn't done for Noble, so this should now be the complete set.
Going ahead and merging this with only one review so we can rebloom what is necessary here. |
Doesn't REP 2000 (https://www.ros.org/reps/rep-2000.html#jazzy-jalisco-may-2024-may-2029) reference 1.13.0 as the PCL version of choice for Jazzy? We were having a discussion on this actually in ros-perception/perception_pcl#448 (comment) for the builds |
Yep, good point. I'll go ahead and update that as well. |
I have a couple of jobs failing
which I would have thought this update would resolve. I don't think I need to run a new release -- but happy to if I'm wrong |
Yeah, you need to re-bloom. Those keys are resolved at bloom-time, so they are hard-coded in the debians incorrectly at this point. |
Ah ok, easy enough! Thanks. I'll wait until tomorrow when I get my email flood to know all the things I need to touch. |
Should I need to cut a new release version in addition to rerunning bloom? When I re-run bloom I get
Where it doesn't list noble in the data (although we all agree its in mainline). Updated, though still on 22.04 - so bloom v0.12.0. |
That shouldn't be necessary.
Hm, that seems like an out-of-date rosdep database. It is in the upstream: Line 4832 in d3ba89e
What package are you trying to release? |
That does appear to be the case. I'm trying to release |
Yeah. For what it is worth, it works here for me; it properly resolves that key to the Can you try running If none of that works, I can do the release for you, but that isn't an ideal situation going forward. |
Done. Still giving me trouble (as expected since that is part of the bloom process), I haven't run into something like this before. Running the release would be appreciated, its a ros2-gbp project so you should have push access. Hopefully this is a transient issue, I've definitely made rosdep changes and immediately run before without issue. If it occurs again after I make the 24.04 migration for Nav2, then I'll look into it more deeply |
I'll go ahead and do the releases. Oh, a couple of other things:
|
Ahhhhh that's it. I had to pin it so that we could make rolling on 22.04 work during the interim that the Rolling migration was having the kinks worked out. So this definitely is a transitory issue. I wouldn't have initially thought that bloom would use that and instead grab the main file given the nature of the operation. But this makes sense. |
@clalancette I got this done - no worries and thanks for the offer. PRs to come. |
Please add the following dependency to the rosdep database.
Package name:
libpcl-*1.14
Package Upstream Source:
🤷
Purpose of using this:
Point cloud stuff
Distro packaging links:
Links to Distribution Packages
Only changing Ubuntu Noble. Fastest way is to search for
libpcl
on this page:But here's all the links: