You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The easiest solution to this problem is to do a new release of pinocchio into ROS 2 Rolling using bloom-release, which should bump the version to 2.7.0.
If you want, you can also do a release of pinocchio 2.7.0 into Jazzy; that is completely up to you.
Please let me know if you have any questions.
The text was updated successfully, but these errors were encountered:
Could you point me to a way to test a release before just running bloom to open a PR ? I have been "just running bloom" a couple time on pinocchio and its dependencies (eigenpy & hpp-fcl), but this is not working better.
For ROS1 (we also have broken packages on noetic), I was using prerelease.ros.org, which was allowing me to fix the ROS patches before opening the PR, but I can't anymore: ros-infrastructure/prerelease_website#65
Could you point me to a way to test a release before just running bloom to open a PR ? I have been "just running bloom" a couple time on pinocchio and its dependencies (eigenpy & hpp-fcl), but this is not working better.
Yeah, unfortunately there isn't currently an easy way. In theory it is possible to do a pre-release type thing following the instructions in https://www.youtube.com/watch?v=XA20_iRBLrg , but I have no idea how well that works anymore.
I'll suggest just doing a bloom-release, and seeing what happens. Totally understood that it isn't the most efficient way, but it is the best I can offer for now.
Currently pinocchio is failing to build on ROS 2 Rolling: https://build.ros2.org/job/Rsrc_uN__pinocchio__ubuntu_noble__source/ .
The easiest solution to this problem is to do a new release of pinocchio into ROS 2 Rolling using
bloom-release
, which should bump the version to 2.7.0.If you want, you can also do a release of pinocchio 2.7.0 into Jazzy; that is completely up to you.
Please let me know if you have any questions.
The text was updated successfully, but these errors were encountered: