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
Hi all! We just switched from OSQP to ProxQP for a project and got some really nice results.
However, we're noticing some behavior changes in the released rosdistro binaries (0.6.5) which are improved in the latest release (0.7.3) -- would the maintainers be willing to bloom new releases for the next sync?
BTW, having gone through this myself, you will probably not be able to bloom a new version of this package to ROS 2 Humble because nanobind-dev is not available as an apt package on Ubuntu 22.04... assuming you are releasing with Python bindings built.
In the case of my project (RoboPlan) I basically am just not supporting Humble for binary releases.
So probably the best bet is to release 0.7.x to Jazzy and newer, and leave Humble at 0.6.x... or if you're not releasing with bindings, you can also ignore me.
Ah yeah, you might also need to get rid of that and instead add a <depend>nanobind-dev</depend>... which again, on Humble it still works via pip install but is just not releasable.
I am not clear if submodules are allowed either... I also went through this with the TOPPRA repo which I was submoduling and instead had to release as its own package.
Hey there, is there already an expected release date?
We're happy with Proxsuite and would like to keep continue using it. But it's non-availability on Kilted and Lyrical is currently blocking us from transitioning. Any chance to do a release of it anytime soon?
Lately I was made aware of the nanobind ABI compatibility. I was previously thinking there were no ABI constraint on nanobind and that we could use any version we want because it will not create any runtime issue.
I think it worth to study if we can support a nanobind minimal version, like we do with other dependencies (usually, we take the minimal version from the oldest Ubuntu LTS, here 22.04). This can help to adopt solution 1.
@jorisv by the way, are you guys planning to release 0.8.0 on PyPI as well? Our library is similarly packaged in a bunch of different ways, and our own PyPI deployment also depends on that... but if that is being dropped for any reason, we can fall back to FetchContent for that.
Activity
sea-bass commentedon Jul 18, 2026
BTW, having gone through this myself, you will probably not be able to bloom a new version of this package to ROS 2 Humble because
nanobind-devis not available as an apt package on Ubuntu 22.04... assuming you are releasing with Python bindings built.In the case of my project (RoboPlan) I basically am just not supporting Humble for binary releases.
So probably the best bet is to release 0.7.x to Jazzy and newer, and leave Humble at 0.6.x... or if you're not releasing with bindings, you can also ignore me.
nim65s commentedon Jul 20, 2026
Hi,
This is currently waiting for ros2-gbp/ros2-gbp-github-org#1075
0.6.5 did not have any python binding.
We can patch them out for humble, or add a FetchContent nanobind as fallback.
sea-bass commentedon Jul 20, 2026
Thanks for the update!
Having also gone through this myself... FetchContent is also disabled on the ROS build farm :)
nim65s commentedon Jul 20, 2026
interesting, I did not know, thanks :)
we still have nanobind as a submodule here, so this should work for now
sea-bass commentedon Jul 20, 2026
Ah yeah, you might also need to get rid of that and instead add a
<depend>nanobind-dev</depend>... which again, on Humble it still works viapip installbut is just not releasable.I am not clear if submodules are allowed either... I also went through this with the TOPPRA repo which I was submoduling and instead had to release as its own package.
Don't you love build systems? 😅
nim65s commentedon Jul 20, 2026
I love the build systems that I can reproduce at home and confidently know if the thing I push has any chance to succeed or not :)
nim65s commentedon Aug 5, 2026
Ok, so for now we have an error even on lyrical:
https://build.ros2.org/job/Lbin_uR64__proxsuite__ubuntu_resolute_amd64__binary/99/console
Because https://github.com/ros2-gbp/proxsuite-release/blob/release/lyrical/proxsuite/package.xml#L29 does not have 2a63ea7#diff-37a67ff78eb7260214b323353263b9af40a2fa98719a1e81937fae0159df87a3R29 yet
So the best solution for this would be to make a new source release, @jorisv, when you are available :)
jorisv commentedon Aug 5, 2026
Can we wait the merge of #437 ? It only missing your green light
sea-bass commentedon Sep 6, 2026
Hi all -- any updates on this? Seems like #437 still has some work left with it.
Would there by any consideration to maybe releasing a 0.7.4 with the current state, and doing other releases later?
mbloechli commentedon Sep 14, 2026
Hey there, is there already an expected release date?
We're happy with Proxsuite and would like to keep continue using it. But it's non-availability on Kilted and Lyrical is currently blocking us from transitioning. Any chance to do a release of it anytime soon?
nim65s commentedon Sep 14, 2026
Yes, this should be unlocked soon
mbloechli commentedon Oct 11, 2026
@nim65s Do you have any news on the expected timeframe of the next release?
nim65s commentedon Oct 11, 2026
the blocker is gone, so @jorisv will probably be able to do that this week
mbloechli commentedon Oct 12, 2026
Thanks, very appreciated!
fix(ci): build proxsuite from source in the upstream workspace
5 remaining items
jorisv commentedon Oct 20, 2026
Lately I was made aware of the nanobind ABI compatibility. I was previously thinking there were no ABI constraint on nanobind and that we could use any version we want because it will not create any runtime issue.
I think it worth to study if we can support a nanobind minimal version, like we do with other dependencies (usually, we take the minimal version from the oldest Ubuntu LTS, here 22.04). This can help to adopt solution 1.
nim65s commentedon Oct 20, 2026
I've open a draft in #489, but I can't remember why
proxsuite/CMakeLists.txt
Line 115 in 592c060
was that not only about stubs ?
maybe CI will tell us
ROS: add nanobind-dev and drop python on humble, fix Simple-Robotics#472
ROS: add nanobind-dev and drop python on humble, fix Simple-Robotics#472
ROS: add nanobind-dev and drop python on humble, fix Simple-Robotics#472
ROS: add nanobind-dev and drop python on humble, fix Simple-Robotics#472
ROS: add nanobind-dev and drop python on humble, fix Simple-Robotics#472
ROS: add nanobind-dev and drop python on humble, fix Simple-Robotics#472
ROS: add nanobind-dev and drop python on humble, fix Simple-Robotics#472
ROS: add nanobind-dev and drop python on humble, fix Simple-Robotics#472
sea-bass commentedon Oct 23, 2026
@jorisv by the way, are you guys planning to release 0.8.0 on PyPI as well? Our library is similarly packaged in a bunch of different ways, and our own PyPI deployment also depends on that... but if that is being dropped for any reason, we can fall back to FetchContent for that.
nim65s commentedon Oct 23, 2026
I was waiting for 0.8.1 to propagate this to PyPI, but yes I believe none of those fixes are relevant there, so I'll do this now
Merge pull request Simple-Robotics#489 from nim65s/ros
jorisv commentedon Oct 28, 2026
0.8.2 is released