-
Notifications
You must be signed in to change notification settings - Fork 524
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
Dependencies missing from deb packages #484
Comments
I see, the package depends for rosbridge_server are broken in 0.11.5. Probably something to do with #460. Maybe the CI needs to be updated to use the new package format. @sfalexrog |
Seems like this doesn't affect melodic, only kinetic. |
Thanks for the reply.
|
Workaround for this is installing the packages listed by @farshbafdoustar (thank you for the list) |
Also requires dependencies:
|
As of today this is affecting melodic packages too. |
👍 also experienced this issue today. does the ros build farm support package format 3 for all previous releases? Is "ROS_PYTHON_VERSION" always set? or should it be defaulting to python2 |
If nobody has answers within a week or so I'm reverting the change that caused this problem and making a release for the next sync. |
I see here: https://github.com/ros/ros_comm/blob/melodic-devel/clients/rospy/package.xml It’s setup very similar, and works. @jacobperron or @wjwwood when/where must ROS_PYTHON_VERSION must be to have the dependencies in the Debs set up properly? ROS1 only uses python2 out of the box so I would assume that is what the debians would ship with python2 for all ROS1 versions, and to use python3 you need to clone export ROS_PYTHON_VERSION, setup a ROS workspace, run rosdep install (this will get the py3 deps) and then compile everything. |
I don't think that matters, but I didn't implement that feature. ros-infrastructure/bloom#551 might have the info you guys need. |
It sounds like maybe we just need to bloom with an up-to-date bloom tool? |
@mvollrath Based on your comment ~4 days ago, this will be fixed in the next kinetic sync. Is that correct? |
The newest kinetic sync occurred over this past weekend. The 0.11.6 version was included and this issue was resolved for me. |
Is there a way we can get this pushed out to Melodic? This breaks things that are automated for me. |
The last melodic sync was on 4/22. I bloomed this fix on 4/29. Follow ROS Discourse for distro sync updates. |
The issue is still there after the latest sync. I'm testing on melodic with release 0.11.9-1 and it's still missing |
I'm using melodic 0.11.9 on Ubuntu and it works and I see this:
What should I do to reproduce? |
This issue has been marked as stale because it has been open for 180 days with no activity. Please remove the stale label or add a comment to keep it open. |
Hello , I ma using ROS neotic on my system. Using the following commands(basically installing the pakages that is not found one by one) helped me solving my error
|
Expected Behavior
rosbridge_websocket running
Actual Behavior
process[rosbridge_websocket-1]: started with pid [122]
Traceback (most recent call last):
File "/opt/ros/kinetic/lib/rosbridge_server/rosbridge_websocket", line 38, in
from twisted.python import log
ImportError: No module named twisted.python
Steps to Reproduce the Problem
....
Setting up ros-kinetic-rosbridge-msgs (0.11.5-1xenial-20200413-135822+0000) ...
Setting up ros-kinetic-rosbridge-server (0.11.5-1xenial-20200413-140154+0000) ...
Setting up ros-kinetic-rosbridge-suite (0.11.5-1xenial-20200413-140413+0000) ...
.....
Specifications
echo $ROS_DISTRO
):kineticgrep DISTRIB_CODENAME /etc/lsb-release
): xenialroscat rosbridge_server package.xml | grep '<version>'
): 0.11.5python -c 'import twisted; print twisted.version'
):Traceback (most recent call last):
File "", line 1, in
ImportError: No module named twisted
The text was updated successfully, but these errors were encountered: