Inject custom vendor packages for Harmonic to avoid Python ABI problems#840
Merged
Inject custom vendor packages for Harmonic to avoid Python ABI problems#840
Conversation
Signed-off-by: Jose Luis Rivero <jrivero@honurobotics.com>
caguero
reviewed
Jul 17, 2025
Collaborator
caguero
left a comment
There was a problem hiding this comment.
I was able to reproduce the issue by running:
rocker --devices /dev/input/js0 --x11 --nvidia --user --home ghcr.io/osrf/vrx-devel:latest /bin/bash
and then inside the container
sudo apt-get update
sudo apt-get upgrade
After compiling VRX, I hit the issue when launching VRX:
caguero@1f7431d4c4df:~/vrx_ws$ ros2 launch vrx_gz competition.launch.py
[INFO] [launch]: All log files can be found below /home/caguero/.ros/log/2025-07-17-22-06-38-861309-1f7431d4c4df-5099
[INFO] [launch]: Default logging verbosity is set to INFO
[ERROR] [launch]: Caught exception in launch (see debug for traceback): Caught multiple exceptions when trying to load file of format [py]:
- ImportError: /usr/lib/python3/dist-packages/sdformat14.cpython-312-x86_64-linux-gnu.so: undefined symbol: _ZNK3sdf3v144Cone14AxisAlignedBoxEv
- InvalidFrontendLaunchFileError: The launch file may have a syntax error, or its format is unknown
Do you have some instructions to verify that this patch fixes the issue?
Collaborator
Author
Oh yes, sorry. cd docker
docker-compose build base devel
rocker --devices /dev/input/js0 --x11 --nvidia --user --home vrx-devel:latest /bin/bashShould leave you in the modified container. |
Closed
exordor
pushed a commit
to exordor/vrx_tunnel
that referenced
this pull request
Oct 26, 2025
…ms (osrf#840) Signed-off-by: Jose Luis Rivero <jrivero@honurobotics.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes: #839
To avoid the installation of the ros-jazzy-gz-*-vendor (being * the Gz packages with Python wrappers) / ros-jazzy-sdformat-vendor packages the PR does the following:
Provides:the vendor packages for the Gazebo libraries that have Python bindings. This way the .deb package dependency chain can continue working without the risk of installing the vendor packages and rosdep can still be used.gztool from ROS to work also with system packages.