Skip to content

New ROS release? #472

Closed
Closed

Description

@sea-bass

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?

Thank you for this fantastic library.

Activity

  1. sea-bass commented on Jul 18, 2026

    @sea-bass
    ContributorAuthor

    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.

  2. nim65s commented on Jul 20, 2026

    @nim65s
    Member

    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.

  3. sea-bass commented on Jul 20, 2026

    @sea-bass
    ContributorAuthor

    Thanks for the update!

    Having also gone through this myself... FetchContent is also disabled on the ROS build farm :)

  4. nim65s commented on Jul 20, 2026

    @nim65s
    Member

    interesting, I did not know, thanks :)

    we still have nanobind as a submodule here, so this should work for now

  5. sea-bass commented on Jul 20, 2026

    @sea-bass
    ContributorAuthor

    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.

    Don't you love build systems? 😅

  6. nim65s commented on Jul 20, 2026

    @nim65s
    Member

    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 :)

  7. nim65s commented on Aug 5, 2026

    @nim65s
    Member

    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

    09:05:20 -- CMAKE_SYSTEM_PROCESSOR: x86_64
    09:05:20 -- [Proxsuite] Using C++ standard: 17
    09:05:20 CMake Error at /usr/share/cmake-4.2/Modules/FindPackageHandleStandardArgs.cmake:290 (message):
    09:05:20   Could NOT find Simde (missing: Simde_INCLUDE_DIR)
    09:05:20 
    09:05:20       Reason given by package: Set BUILD_WITH_VECTORIZATION_SUPPORT=OFF or install Simde on your system.
    09:05:20    If Simde is already installed, ensure that the CMake variable CMAKE_MODULE_PATH correctly points toward the location of FindSimde.cmake file.
    09:05:20 
    09:05:20 Call Stack (most recent call first):
    09:05:20   /usr/share/cmake-4.2/Modules/FindPackageHandleStandardArgs.cmake:654 (_FPHSA_FAILURE_MESSAGE)
    09:05:20   cmake-module/find-external/Simde/FindSimde.cmake:20 (find_package_handle_standard_args)
    09:05:20   cmake-module/package-config.cmake:114 (find_package)
    09:05:20   CMakeLists.txt:187 (ADD_PROJECT_DEPENDENCY)
    09:05:20 
    09:05:20 
    09:05:20 -- Configuring incomplete, errors occurred!
    09:05:20 	cd .obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt

    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 :)

  8. jorisv commented on Aug 5, 2026

    @jorisv
    Contributor

    Can we wait the merge of #437 ? It only missing your green light

  9. sea-bass commented on Sep 6, 2026

    @sea-bass
    ContributorAuthor

    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?

  10. mbloechli commented on Sep 14, 2026

    @mbloechli

    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?

  11. nim65s commented on Sep 14, 2026

    @nim65s
    Member

    Yes, this should be unlocked soon

  12. mbloechli commented on Oct 11, 2026

    @mbloechli

    @nim65s Do you have any news on the expected timeframe of the next release?

  13. nim65s commented on Oct 11, 2026

    @nim65s
    Member

    the blocker is gone, so @jorisv will probably be able to do that this week

  14. mbloechli commented on Oct 12, 2026

    @mbloechli

    Thanks, very appreciated!

  15. 5 remaining items

  16. jorisv commented on Oct 20, 2026

    @jorisv
    Contributor

    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.

  17. nim65s commented on Oct 20, 2026

    @nim65s
    Member

    I've open a draft in #489, but I can't remember why

    # - Ubuntu 24.04 ships an incompatible 1.9.2 version of nanobind via apt-get.

    was that not only about stubs ?
    maybe CI will tell us

  18. added 8 commits that reference this issue on Oct 20, 2026
    e57e5f7
    4dabfa1
    d2e6016
    ea29960
    33770b6
    7f9be8a
    899922e
    9fd271c
  19. sea-bass commented on Oct 23, 2026

    @sea-bass
    ContributorAuthor

    @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.

  20. nim65s commented on Oct 23, 2026

    @nim65s
    Member

    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

  21. added a commit that references this issue on Oct 27, 2026
    73fcb96
  22. jorisv commented on Oct 28, 2026

    @jorisv
    Contributor

    0.8.2 is released

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions