Revision history [back]

Eh, figured out the issue. manifest.xml was renamed to package.xml and rospkg/rospack.py on my system is still the old version which is looking for manifest.xml so it thinks I have no packages installed. For the time being I'm going to just stick the newest version of rospkg from github (https://github.com/ros/rospkg) on my PYTHONPATH ahead of everything else. To add a question to a question though, is there an updated deb for python-rospkg or is this the best way to work on Groovy stuff right now?

Eh, figured out the issue. manifest.xml was renamed to package.xml and rospkg/rospack.py on my system is still the old version which is looking for manifest.xml so it thinks I have no packages installed. For the time being I'm going to just stick the newest version of rospkg from github (https://github.com/ros/rospkg) on my PYTHONPATH ahead of everything else. To add a question to a question though, is there an updated deb for python-rospkg or is this the best way to work on Groovy stuff right now?

Eh, figured out the issue. manifest.xml was renamed to package.xml and rospkg/rospack.py on my system is still the old version which is looking for manifest.xml so it thinks I have no packages installed. For the time being I'm going to just stick the newest version of rospkg from github (https://github.com/ros/rospkg) on my PYTHONPATH ahead of everything else. To add a question to a question though, is there an updated deb for python-rospkg or is this the best way to work on Groovy stuff right now?

Actually, I think the proper solution for now is to use virtualenv? I thought maybe I could install an updated version of rospkg without messing with the system version but setuptools isn't cooperating.