From ros/rosdistro#438 ros/rosdistro#58

I've fielded several questions and there have been multiple tickets related to new rosdeps that just need a rosdep update.

I know this tools slated for deprecation, but it'll be around for the next few weeks and in that time there will still be lots of questions.

BTW the existing error has made people ask about how to get dependency_name.yaml they haven't even known to look for rosdep.yaml. I don't know if that's reader error, but that's what the people coming by my office have been asking.

trac data:

• Owner: mquigley
• Reporter: tfoote
• Reported at: Wed Aug 12 10:23:31 2009
• URL: http://code.ros.org/trac/ros/ticket/1577

If some directories which are already listed in the ROS_PACKAGE_PATH don't exist yet, because the complete system is not yet installed it fails:

$ rosdep install --from-paths src --ignore-src -s

ERROR: Rosdep experienced an internal error: given path '/opt/ros/groovy/stacks' does not exist
Please go to the rosdep page [1] and file a bug report with the stack trace below.
[1] : http://www.ros.org/wiki/rosdep

Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/rosdep2/main.py", line 116, in rosdep_main
exit_code = _rosdep_main(args)
File "/usr/local/lib/python2.7/dist-packages/rosdep2/main.py", line 257, in _rosdep_main
return _package_args_handler(command, parser, options, args)
File "/usr/local/lib/python2.7/dist-packages/rosdep2/main.py", line 327, in _package_args_handler
pkgs = find_catkin_packages_in(path, options.verbose)
File "/usr/local/lib/python2.7/dist-packages/rosdep2/catkin_packages.py", line 24, in find_catkin_packages_in
raise OSError("given path '{0}' does not exist".format(path))
OSError: given path '/opt/ros/groovy/stacks' does not exist

Now rosdep only uses ROS_DISTRO in the env. A command line option would be nice.

With the new structure we're not guarenteed uniqueness of packages.

rosdep should store the version of rosdep in the database. When it queries the database and the version is different an update should be enforced.

This is crucial when rosdep is changed, since it might require an updated db format.

When running the tests for rosdep I get this:

======================================================================
ERROR: testIssue30 (test.test_rosdep_issue30.Issue30TestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/william/devel/rosdep/test/test_rosdep_issue30.py", line 28, in testIssue30
    keys = rdmain.get_keys(lookup, ['spacenav_node'], recursive=True)
  File "/Users/william/devel/rosdep/src/rosdep2/main.py", line 364, in get_keys
    deps = lookup.get_rosdeps(package_name, implicit=recursive)
  File "/Users/william/devel/rosdep/src/rosdep2/lookup.py", line 250, in get_rosdeps
    return self.loader.get_rosdeps(resource_name, implicit=implicit)
  File "/Users/william/devel/rosdep/src/rosdep2/rospkg_loader.py", line 140, in get_rosdeps
    raise rospkg.ResourceNotFound(resource_name)
ResourceNotFound: spacenav_node

This is most likely because I am not in a ROS environment. It seems like some assumptions were made in order to do this test which don't hold everywhere (like my mac book in a clean terminal and on the CI server). Also depending on a particular git repository controlled by someone else to not change is probably fragile, maybe we should tar that git repo up and extract it for the tests.

it does not make sense to me that the rosdep cache is stored on a per-user basis

Making the cache optionally storable in /etc/ros/rosdep/sources.cache seems like a better idea, and it could be made updatable by making it group writeable by group 'ros'

Write basic tests, at least making sure that it runs successfully when given good input.

trac data:

• Owner: tfoote
• Reporter: gerkey
• Reported at: Tue Jul 28 17:53:50 2009
• URL: http://code.ros.org/trac/ros/ticket/1469

{{{
tfoote@axx:/home/tfoote/stable_ros/ros-pkg/stacks/visual_feature_detectors/checkerboard_detector$ rosdep install ogre
sh: scripts/satisfy: Permission denied
tfoote@axx:/home/tfoote/stable_ros/ros-pkg/stacks/visual_feature_detectors/checkerboard_detector$ rosdep satisfy ogre
couldn't find a rosdep.yaml entry for freeimage
tfoote@axx:/home/tfoote/stable_ros/ros-pkg/stacks/visual_feature_detectors/checkerboard_detector$ rosdep update
backing up your current rosdep.yaml file to /home/tfoote/stable_ros/ros/tools/rosdep/rosdep.yaml.2009-08-07-20-28-25
downloading the latest rosdep.yaml from sourceforge...
dependency database updated successfully.
tfoote@axx:/home/tfoote/stable_ros/ros-pkg/stacks/visual_feature_detectors/checkerboard_detector$ rosdep satisfy ogre

!/bin/bash

set -o errexit
set -o verbose

sudo apt-get -y install libzzip-0-13 libzzip-dev libxaw7-dev libgl1-mesa-dev libglu1-mesa-dev libxxf86vm-dev libgtk2.0-dev libfreeimage-dev nvidia-cg-toolkit

tfoote@axx:/home/tfoote/stable_ros/ros-pkg/stacks/visual_feature_detectors/checkerboard_detector$ rosdep install ogre
sh: scripts/satisfy: Permission denied
tfoote@axx:/home/tfoote/stable_ros/ros-pkg/stacks/visual_feature_detectors/checkerboard_detector$ sudo rosdep install ogre
[sudo] password for tfoote:
sudo: rosdep: command not found
tfoote@axx:/home/tfoote/stable_ros/ros-pkg/stacks/visual_feature_detectors/checkerboard_detector$ bash <(rosdep satisfy ogre)

sudo apt-get -y install libzzip-0-13 libzzip-dev libxaw7-dev libgl1-mesa-dev libglu1-mesa-dev libxxf86vm-dev libgtk2.0-dev libfreeimage-dev nvidia-cg-toolkit
Reading package lists... Done
Building dependency tree
Reading state information... Done
libzzip-0-13 is already the newest version.
libzzip-dev is already the newest version.
libxaw7-dev is already the newest version.
libgl1-mesa-dev is already the newest version.
libglu1-mesa-dev is already the newest version.
libxxf86vm-dev is already the newest version.
libgtk2.0-dev is already the newest version.
libfreeimage-dev is already the newest version.
libfreeimage-dev set to manually installed.
The following packages were automatically installed and are no longer required:
libopenexr-dev libilmbase-dev
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
nvidia-cg-toolkit
}}}

trac data:

• Owner: mquigley
• Reporter: tfoote
• Reported at: Fri Aug 7 20:29:54 2009
• URL: http://code.ros.org/trac/ros/ticket/1551

Not a catkin expert yet but this should be possible.

Since we are installing rosdep via packages we should be able to have a debian/postinstall that runs
'rosdep init'

This proposed federated model for rosdep will lock in common dependencies, but allow higher-level "distributions" (e.g. WG PR2,
Stanford STAIR, Bosch Foo, CMU Bar) to define higher level 3rdparty
dependencies in an independent manner.

rosdep.yaml:

1. Each stack has a rosdep.yaml
2. A repo can also have a rosdep.yaml

resolving "rosdep satisfy foo":

1. Go to the 'foo' package
2. Search upwards until a rosdep.yaml is found
3. If a stack.xml is found next to it, load all the rosdep.yamls of the dependencies first. If there is a conflict, i.e. multiple rosdep.yamls define the same key, this is a FATAL error.

The one loophole right now is what to do about the rosdep.yaml for a
repository, as this proposal is very stack-based. The answer there is either to:

a. require that outside institutions turn their repos into temporary Stacks by adding a top-level stack.xml, e.g. the sail-ros-pkg 'Stack'
b. add syntax directly to rosdep.yaml to also allow it to specify a dependent stack.

I think I am leaning towards (a), even if it means an ugly transitional period where entire repos are stacks. In the long term, when everything is in a proper stack, this will be much cleaner.

The approach does much of what a Linux distribution does, but in a
slightly more federated model. ROS naturally defines what boost has to be for all other dependencies of it. There are similar such
definitions created in lower level stacks that higher level stacks
must adopt if they wish to depend on those stacks. But it also allows outside institutions to do the same work that we are doing here, i.e. defining the common libraries for work within their institution and enforcing it within their distribution.

The other benefits of this approach are:

1. The rosdep.yaml is versioned with each release
2. rosdep.yaml files will generally be very stable as people will generally modify the trunk version of their own rosdep.yaml prior to
   release
3. stack owners retain control over the definitions of their dependencies that they introduce. Similarly, it is easier to assign responsibility for a particular dependency to a particular person

NOTE: this approach does not preclude having a Web service in the
future that does the work of extending the ability of the community to provide key->installation mappings. One possible way we could do this is define a new type of entry in the rosdep.yaml file, such as:

magicservice: boost

Which says that instead of matching a platform key, load the platform keys from magicservice.

trac data:

• Owner: mquigley
• Reporter: kwc
• Reported at: Wed Jul 29 15:45:10 2009
• URL: http://code.ros.org/trac/ros/ticket/1495

If you run rosdep update before rosdep init on Lucid you get:

∫ rosdep update

ERROR: Rosdep experienced an internal error: [Errno 2] No such file or directory: '/etc/ros/rosdep/sources.list.d'
Please go to the rosdep page [1] and file a bug report with the stack trace below.
[1] : http://www.ros.org/wiki/rosdep

Traceback (most recent call last):
  File "/usr/local/lib/python2.6/dist-packages/rosdep2/main.py", line 111, in rosdep_main
    exit_code = _rosdep_main(args)
  File "/usr/local/lib/python2.6/dist-packages/rosdep2/main.py", line 230, in _rosdep_main
    return _no_args_handler(command, parser, options, args)
  File "/usr/local/lib/python2.6/dist-packages/rosdep2/main.py", line 238, in _no_args_handler
    return command_handlers[command](options)
  File "/usr/local/lib/python2.6/dist-packages/rosdep2/main.py", line 341, in command_update
    filelist = [f for f in os.listdir(sources_list_dir) if f.endswith('.list')]
OSError: [Errno 2] No such file or directory: '/etc/ros/rosdep/sources.list.d'

This should probably be a little nicer error message.

As groovy is coming up there are going to be a bunch of people needing to add the groovy gbp repo to rosdeps sources.

apt-add-repository is a very easy way to do that for debian sources. Something similar would be useful.

Please add a LICENSE file with the BSD license text to rosdep's source tree.

running sudo rosdep init twice should update the list of sources instead of throwing an error

$ sudo rosdep init
Wrote /etc/ros/rosdep/sources.list.d/20-default.list
Recommended: please run

    rosdep update

$ sudo rosdep init
ERROR: default sources list file already exists:
    /etc/ros/rosdep/sources.list.d/20-default.list
Please delete if you wish to re-initialize

on the farm, this can happen:

Updating certificates in /etc/ssl/certs... 151 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d....done.
--2012-11-17 19:04:36-- https://code.ros.org/svn/release/download/stacks/filters/filters-1.6.0/filters-1.6.0.tar.bz2
Resolving code.ros.org (code.ros.org)... 70.35.54.198
Connecting to code.ros.org (code.ros.org)|70.35.54.198|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 16996 (17K) [application/octet-stream]
Saving to: `/tmp/buildd/filters-1.6.0.tar.bz2'

 0K .......... ......                                     100%  237K=0.07s

2012-11-17 19:04:36 (237 KB/s) - `/tmp/buildd/filters-1.6.0.tar.bz2' saved [16996/16996]

ERROR: unable to process source [https://github.com/ros/rosdistro/raw/master/rosdep/osx-homebrew.yaml]:

ERROR: unable to process source [https://github.com/ros/rosdistro/raw/master/releases/groovy.yaml]:
Failed to download target platform data for gbpdistro:

reading in sources list data from /etc/ros/rosdep/sources.list.d
Hit https://github.com/ros/rosdistro/raw/master/rosdep/gentoo.yaml
Hit https://github.com/ros/rosdistro/raw/master/rosdep/base.yaml
Hit https://github.com/ros/rosdistro/raw/master/rosdep/python.yaml
Hit https://github.com/ros/rosdistro/raw/master/rosdep/ruby.yaml
Hit https://github.com/ros/rosdistro/raw/master/releases/fuerte.yaml
updated cache in /tmp/buildd/.ros/rosdep/sources.cache

apt

libgtest-dev
I: user script /tmp/tmpiKJii0/pbuilder/29105/tmp/hooks/A50fetch finished

For example, PyYAML and log4cxx try to put stuff in ~/ros/ros-deps.

This should probably be $ROS_ROOT/ros-deps, or maybe some other environment variable.

trac data:

• Owner: mquigley
• Reporter: leibs
• Reported at: Mon Jul 20 11:39:05 2009
• URL: http://code.ros.org/trac/ros/ticket/1404

festival ubuntu festival
festvox-kallpc16k ubuntu festvox-kallpc16k

(festvox-kallpc16k is one of festival voices. It is a reasonable choice of name for this package, but something more generic may be desirable. I don't know, for example if other distributions have the same selection of names so festvox-voice might be preferable for this rosdep name)

trac data:

• Owner: mquigley
• Reporter: blaise
• Reported at: Thu Aug 6 17:33:53 2009
• URL: http://code.ros.org/trac/ros/ticket/1543

libxrandr ubuntu libxrandr-dev

trac data:

• Owner: mquigley
• Reporter: anonymous
• Reported at: Thu Sep 3 05:44:22 2009
• URL: http://code.ros.org/trac/ros/ticket/1680

I have been working on getting ROS to compile on OSX 10.5.7 and I had to add the following to ros/tools/rosdep/rosdep.yaml

fltk:
macports: fltk

automake:
macports: automake

python-imaging:
macports: py25-pil

NOTE: py-pil is for python 2.4

sdl:
macports: libsdl

sdl-image:
macports: libsdl_image

libxext:
macports: xorg-libXext

python-numpy:
macports: py25-numpy

again py-numpy is for python 2.4

glut:
macports: glut

graphviz:
macports: graphviz

autoconf:
macports: autoconf

This has gotten me further, but I am now getting more errors:

eval "export ROS_ROOT=/Users/avoot/ros/ros ; export PATH=/Users/avoot/ros/ros/bin:${PATH} ; export PYTHONPATH=/Users/avoot/ros/ros/core/roslib/src:${PYTHONPATH} ; export OCTAVE_PATH=/Users/avoot/ros/ros/core/experimental/rosoct/octave:${OCTAVE_PATH} ; if [ ! "$ROS_MASTER_URI" ] ; then export ROS_MASTER_URI=http://localhost:11311 ; fi ; export ROS_PACKAGE_PATH=/Users/avoot/ros/ros-pkg ; export ROS_STACK_PATH=/Users/avoot/ros/ros:/Users/avoot/ros/ros-pkg ; . /Users/avoot/ros/ros/tools/rosbash/rosbash " && rosdep satisfy roslaunch move_base_stage > /Users/avoot/ros/.rosdep_satisfy_script
terminate called after throwing an instance of 'YAML::ParserException'
what(): N4YAML15ParserExceptionE
/bin/sh: line 1: 45860 Abort trap rosdep satisfy roslaunch move_base_stage > /Users/avoot/ros/.rosdep_satisfy_script
failed to install roslaunch via rosdep [exit code 134]

Thanks

trac data:

• Owner: mquigley
• Reporter: avoot [aht] colby [.] edu
• Reported at: Wed Jul 1 08:28:33 2009
• URL: http://code.ros.org/trac/ros/ticket/1330

The current python-rosdep package in ubuntu precise fails with the following error:
ImportError: No module named catkin_pkg.package

It can be solved by manually installing python-catkin-pkg but the dependency should be explicitly added to python-rosdep.

This should be fixed, but it isn't a 1 to 1 with rosdep so I couldn't easily convert it

trac data:

• Owner: mquigley
• Reporter: tfoote
• Reported at: Wed Jul 22 15:37:46 2009
• URL: http://code.ros.org/trac/ros/ticket/1431

Patch attached to https://code.ros.org/trac/ros/ticket/4050

Rather than failing and not doing anything when a package can't be resolved, instead install all packages that we could find, warn, and continue.

Behavior should be toggle-able.

Consider:

mkdir ~/catkin_ws
cd ~/catkin_ws
wstool init src http://packages.ros.org/web/rosinstall/generate/raw/groovy/desktop

If I then run something like this:

ROS_PACKAGE_PATH=`pwd`/src rosdep keys geometry_msgs

I get:

std_msgs
langs-dev
langs
genmsg
catkin

Which is correct, but if I were to run something like:

ROS_DISTRO=groovy rosdep install std_msgs -s

I get:

#[homebrew] Installation commands:
  brew install ros/groovy/langs-dev
  brew install ros/groovy/catkin
  brew install ros/groovy/genmsg
  brew install ros/groovy/langs

Which again is technically correct, but since those are in my catkin workspace it should consider it 'resolved' and not try to install it. So maybe something like this:

ROS_PACKAGE_PATH=`pwd`/src ROS_DISTRO=groovy rosdep install std_msgs -s

Would not try to install anything, because it found those dependencies in source on my ROS_PACKAGE_PATH.

The boost and log4cxx entries in rosdep.yaml are hard-coded to look in /opt/ros.

trac data:

• Owner: mquigley
• Reporter: mihelich
• Reported at: Thu Jul 30 18:35:22 2009
• URL: http://code.ros.org/trac/ros/ticket/1502

I ran rosdep install prosilica_cam got it failed to finish

{{{
mwise@aqy:~/ros/ros-pkg/stacks/sound_drivers/sound_play$ rosdep install prosilica_cam

sudo apt-get -y install libapr1-dev libaprutil1-dev python-dev python-yaml libbz2-dev zlib1g-dev python-imaging libavformat-dev libavcodec-dev libjasper-dev libswscale-dev libgraphicsmagick++1-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libapr1-dev is already the newest version.
libaprutil1-dev is already the newest version.
python-dev is already the newest version.
python-yaml is already the newest version.
libbz2-dev is already the newest version.
zlib1g-dev is already the newest version.
python-imaging is already the newest version.
libavformat-dev is already the newest version.
libavcodec-dev is already the newest version.
libjasper-dev is already the newest version.
libswscale-dev is already the newest version.
libgraphicsmagick++1-dev is already the newest version.
The following packages were automatically installed and are no longer required:
xserver-xorg-video-amd dvipng python-enthought-traits python-configobj blt
python-tk python-tz libt1-5 python-matplotlib-data libsdl-ttf2.0-0
linux-headers-2.6.24-23-generic python-dateutil tcl8.4 libsdl-mixer1.2 tk8.4
python-matplotlib libestools1.2 linux-headers-2.6.24-23 libsmpeg0
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 70 not upgraded.
2 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Setting up python-tz (2007k-0ubuntu2) ...
pycentral: pycentral pkginstall: not overwriting local files
pycentral pkginstall: not overwriting local files
dpkg: error processing python-tz (--configure):
subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of python-matplotlib:
python-matplotlib depends on python-tz; however:
Package python-tz is not configured yet.
dpkg: error processing python-matplotlib (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
python-tz
python-matplotlib
E: Sub-process /usr/bin/dpkg returned an error code (1)
}}}

trac data:

• Owner: mquigley
• Reporter: mwise
• Reported at: Fri Aug 14 11:26:56 2009
• URL: http://code.ros.org/trac/ros/ticket/1593

Hi,

I think there is a problem when rosdep is run as root, because root has no command sudo.

Here is the full error message:
executing command [sudo apt-get install libjson-glib-dev]

ERROR: Rosdep experienced an internal error: [Errno 2] No such file or directory
Please go to the rosdep page [1] and file a bug report with the stack trace below.
[1] : http://www.ros.org/wiki/rosdep

Traceback (most recent call last):
File "/usr/lib/pymodules/python2.7/rosdep2/main.py", line 116, in rosdep_main
exit_code = _rosdep_main(args)
File "/usr/lib/pymodules/python2.7/rosdep2/main.py", line 257, in _rosdep_main
return _package_args_handler(command, parser, options, args)
File "/usr/lib/pymodules/python2.7/rosdep2/main.py", line 338, in _package_args_handler
return command_handlers[command](lookup, packages, options)
File "/usr/lib/pymodules/python2.7/rosdep2/main.py", line 494, in command_install
installer.install(uninstalled, *_install_options)
File "/usr/lib/pymodules/python2.7/rosdep2/installers.py", line 477, in install
verbose=verbose)
File "/usr/lib/pymodules/python2.7/rosdep2/installers.py", line 526, in install_resolved
result = subprocess.call(sub_command)
File "/usr/lib/python2.7/subprocess.py", line 493, in call
return Popen(_popenargs, **kwargs).wait()
File "/usr/lib/python2.7/subprocess.py", line 679, in init
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1249, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory

I am getting different results in this two cases, where i think the programm should act in the same way:

case 1: "rosdep install -a --os="debian:squeeze"
case 2: "rosdep install -a" with the ROS_OS_OVERRIDE environment variable set to "debian:squeeze"

I suppose, in case 1 rosdep is working correctly, while in case 2 i get the following error for a example:
package: No definiton of [boost] for OS version[]

It would be a great extension to allow definitions for installing from multiple installers if possible and let the user define their preferences in order.

Possibly also allow pip and gem to be at a higher level outside the platform specific tags as a fallback if no specific rule is defined.

This will help people avoid tracebacks

{{{
jfaust@arx:~/ros/ros$ rosdep install all
terminate called after throwing an instance of 'std::runtime_error'
what(): couldn't find package [all]

}}}

trac data:

• Owner: mquigley
• Reporter: jfaust
• Reported at: Fri Aug 7 10:59:54 2009
• URL: http://code.ros.org/trac/ros/ticket/1548

pypa/pip#588

If you update the sources.list it doesn't reread the values before updating the databases.

if you check out a fresh tree with rosdep adn try to rosdep install something you get this

{{{
$ rosdep install ps3joy
sh: scripts/satisfy: Permission denied
}}}

this happens because satisfy script is not checked in as executable.

trac data:

• Owner: mquigley
• Reporter: mwise
• Reported at: Mon Aug 17 14:42:35 2009
• URL: http://code.ros.org/trac/ros/ticket/1599

The case where I am managing the dependency manually, with no need for rosdep to try to install it.

For an example, see portage's "package.provided". An excerpt from "http://dev.gentoo.org/~zmedico/portage/doc/man/portage.5.html":

 For example, if you manage your own copy of a 2.6 kernel, then you  can  tell  portage  that
'sys-kernel/development-sources-2.6.7'  is  already taken care of and it should get off your
back about it.

Note that on a system using portage, I can create a fake ebuild (portage package), a fake rosdep mapping to it, and then add it to package.provided to get this effect, but I'm looking for support directly in portage (so the various fake items above can be removed).

Once #46 is implemented, we should be able to automatically update a system wide rosdep cache.

Possible solutions

1. make the cache available as a separate package we can update automatically via the package manager

2. Use debconf and dplg-reconfigure to allow users to enable a weekly(?) cronjob to pull down rosdep cache updates
   This ensures that the user consents to running a cron that accesses the network

when rosdep updates the database is in an incomplete state during the operation which lets concurrent operations potentially fail.

I don't see any equivalent on my machine in a quick search. rosdep is currently keyed to all of ubuntu, but it appears this needs to be broken down. Busy migrating messages but don't want to forget this

trac data:

• Owner: mquigley
• Reporter: kwc
• Reported at: Fri Aug 7 21:26:59 2009
• URL: http://code.ros.org/trac/ros/ticket/1552

Here is a patch for the rosdep package to add support for gentoo, I've
included a preinstall.gentoo file that should mimic the functionality
of the preinstall.ubuntu. Here's and overview of what I've done:

1. modified os.cpp to find /etc/gentoo-releases (no funky stuff to
   find versions yet) to confirm a gentoo environment
2. modified os.cpp to prepend 'sudo emerge -u' to the package list,
   this will update a package or install it if it is not currently
   installed, but will do nothing if the package is already installed at
   the full version
3. modified rosdep.yaml to add gentoo rules to satisfy roscpp and
   gazebo, should be enough to make an effective install script.
4. created preinstall.gentoo which will emerge
   Enjoy.

Here is what is left over:

1. There are some packages that are "masked", where certain version
   numbers are disallowed, while others are not, it would be great if the
   script could automatically unmask packages, when needed. I'm still
   working on that.
2. there are a lot of rules that I have not filled in, and probably
   won't on my own, I just wanted to clear the way for an install script

-Dave

trac data:

• Owner: mquigley
• Reporter: kwc
• Reported at: Wed Aug 12 10:31:46 2009
• URL: http://code.ros.org/trac/ros/ticket/1579

[ moldy-crow: ~/versioned/ros/maintain_catkin/ws/build ] source buildspace/setup.sh 
[ moldy-crow: ~/versioned/ros/maintain_catkin/ws/build ] roscd spacenav_node/
[ moldy-crow: ~/versioned/ros/maintain_catkin/ws/src/joystick_drivers/spacenav_node ] rosdep keys spacenav_node

[ moldy-crow: ~/versioned/ros/maintain_catkin/ws/src/joystick_drivers/spacenav_node ] 

This package should list libspnav-dev and spacenavd as rosdeps.

Running rosdep resolve PKG in a ROS groovy environments yields ros-fuerte-PKG instead of ros-groovy-PKG for a package released with bloom (octomap). This was after I manually extended /etc/ros/rosdep/sources.list.d/20-default.list with the line
gbpdistro https://github.com/ros/rosdistro/raw/master/releases/groovy.yaml groovy
and ran rosdep update.

As a result, running the release script for a groovy package results in an invalid release that depends on the wrong debian package of PKG which will fail building.

#4070: (fuerte) rosdep install -a FAILS

---------------------------+------------------------------------------------
Reporter: jay | Owner: tfoote
Type: defect | Status: new
Priority: major | Milestone: fuerte-release
Component: rosdep | Version:
Keywords: | Include_gantt: 0
Dependencies: | Due_assign: DD/MM/YYYY
Due_close: DD/MM/YYYY |
---------------------------+------------------------------------------------
I'm installing ROS from source on Debian testing following the Debian
install instructions. I get the following error when running rosdep for
the first time (http://www.ros.org/wiki/fuerte/Installation/Debian Step
1.5)

$ rosdep install -a

ERROR: Rosdep experienced an internal error: Directory
"/opt/ros/fuerte/share/wxPython_swig_interface" does not contain a
"package.xml"
Please go to the rosdep page [1] and file a bug report with the stack
trace below.
[1] : http://www.ros.org/wiki/rosdep

Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/rosdep2/main.py", line 116,
in rosdep_main
exit_code = _rosdep_main(args)
File "/usr/local/lib/python2.7/dist-packages/rosdep2/main.py", line 257,
in _rosdep_main
return _package_args_handler(command, parser, options, args)
File "/usr/local/lib/python2.7/dist-packages/rosdep2/main.py", line 338,
in _package_args_handler
return command_handlers[command](lookup, packages, options)
File "/usr/local/lib/python2.7/dist-packages/rosdep2/main.py", line 483,
in command_install
uninstalled, errors = installer.get_uninstalled(packages,
implicit=options.recursive, verbose=options.verbose)
File "/usr/local/lib/python2.7/dist-packages/rosdep2/installers.py",
line 401, in get_uninstalled
resolutions, errors = self.lookup.resolve_all(resources,
installer_context, implicit=implicit)
File "/usr/local/lib/python2.7/dist-packages/rosdep2/lookup.py", line
348, in resolve_all
rosdep_keys = self.get_rosdeps(resource_name, implicit=implicit)
File "/usr/local/lib/python2.7/dist-packages/rosdep2/lookup.py", line
270, in get_rosdeps
return self.loader.get_rosdeps(resource_name, implicit=implicit)
File "/usr/local/lib/python2.7/dist-packages/rosdep2/rospkg_loader.py",
line 131, in get_rosdeps
pkg = catkin_pkg.package.parse_package(path)
File "/usr/local/lib/python2.7/dist-packages/catkin_pkg/package.py",
line 251, in parse_package
raise IOError('Directory "%s" does not contain a "%s"' % (path,
PACKAGE_MANIFEST_FILENAME))
IOError: Directory "/opt/ros/fuerte/share/wxPython_swig_interface" does
not contain a "package.xml"

When working with catkin workspaces it would be nice to easily specify the src folder and have rosdep act on all of those packages there in. Consider:

mkdir -p ~/ros_core_ws
cd ~/ros_core_ws
wstool init src http://packages.ros.org/web/rosinstall/generate/raw/groovy/desktop

Then I would like to do things like this:

rosdep keys --catkin-workspace ./src
rosdep install --catkin-workspace ./src

Or maybe like this:

rosdep install --from-path ./src
OR
rosdep install --all-in-path ./src

This optional argument, whatever it is called, will cause rosdep to consider the positional argument(s) given to the rosdep verb as a folder containing packages.

Open question:
Should this work for a folder of rosbuild packages/stacks not on the ROS_PACKAGE_PATH (or on it for that matter)?

This is really needed for the source install instructions.

I see the update, but no documentation I cannot find

trac data:

• Owner: mquigley
• Reporter: kwc
• Reported at: Thu Jul 30 18:55:31 2009
• URL: http://code.ros.org/trac/ros/ticket/1503

dpkg-reconfigure should rerun rosdep init or update the files directly, so when hydro or later comes out and someone runs apt-get upgrade it should actually update the default list of sources instead of leaving this as a challenge for the user to debug.

Was: Failed to detect wheezy OS running rosdep on raspberry

I was stepping through the generic source installation steps to try and install groovy on a raspberry pi.

At step 2.1.3 I ran the command rosdep and failed to find (in my case override) the OS.

pi@raspberrypi ~/ros_catkin_ws $ rosdep install --os=debian:wheezy --from-paths src --ignore-src --rosdistro groovy -y

ERROR: Rosdep experienced an internal error: Could not detect OS, tried ['ubuntu', 'rhel', 'osx', 'opensuse', 'mint', 'gentoo', 'freebsd', 'fedora', 'debian', 'cygwin', 'arch']
Please go to the rosdep page [1] and file a bug report with the stack trace below.
[1] : http://www.ros.org/wiki/rosdep

Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/rosdep-0.10.11-py2.7.egg/rosdep2/main.py", line 116, in rosdep_main
    exit_code = _rosdep_main(args)
  File "/usr/local/lib/python2.7/dist-packages/rosdep-0.10.11-py2.7.egg/rosdep2/main.py", line 257, in _rosdep_main
    return _package_args_handler(command, parser, options, args)
  File "/usr/local/lib/python2.7/dist-packages/rosdep-0.10.11-py2.7.egg/rosdep2/main.py", line 338, in _package_args_handler
    return command_handlers[command](lookup, packages, options)
  File "/usr/local/lib/python2.7/dist-packages/rosdep-0.10.11-py2.7.egg/rosdep2/main.py", line 483, in command_install
    uninstalled, errors = installer.get_uninstalled(packages, implicit=options.recursive, verbose=options.verbose)
  File "/usr/local/lib/python2.7/dist-packages/rosdep-0.10.11-py2.7.egg/rosdep2/installers.py", line 401, in get_uninstalled
    resolutions, errors = self.lookup.resolve_all(resources, installer_context, implicit=implicit)
  File "/usr/local/lib/python2.7/dist-packages/rosdep-0.10.11-py2.7.egg/rosdep2/lookup.py", line 348, in resolve_all
    rosdep_keys = self.get_rosdeps(resource_name, implicit=implicit)
  File "/usr/local/lib/python2.7/dist-packages/rosdep-0.10.11-py2.7.egg/rosdep2/lookup.py", line 270, in get_rosdeps
    return self.loader.get_rosdeps(resource_name, implicit=implicit)
  File "/usr/local/lib/python2.7/dist-packages/rosdep-0.10.11-py2.7.egg/rosdep2/rospkg_loader.py", line 128, in get_rosdeps
    m = self._rospack.get_manifest(resource_name)
  File "/usr/local/lib/python2.7/dist-packages/rospkg-1.0.17-py2.7.egg/rospkg/rospack.py", line 133, in get_manifest
    return self._load_manifest(name)
  File "/usr/local/lib/python2.7/dist-packages/rospkg-1.0.17-py2.7.egg/rospkg/rospack.py", line 172, in _load_manifest
    retval = self._manifests[name] = parse_manifest_file(self.get_path(name), self._manifest_name)
  File "/usr/local/lib/python2.7/dist-packages/rospkg-1.0.17-py2.7.egg/rospkg/manifest.py", line 376, in parse_manifest_file
    _static_rosdep_view = init_rospack_interface()
  File "/usr/local/lib/python2.7/dist-packages/rosdep-0.10.11-py2.7.egg/rosdep2/rospack.py", line 55, in init_rospack_interface
    lookup = _get_default_RosdepLookup(Options())
  File "/usr/local/lib/python2.7/dist-packages/rosdep-0.10.11-py2.7.egg/rosdep2/main.py", line 107, in _get_default_RosdepLookup
    verbose=options.verbose)
  File "/usr/local/lib/python2.7/dist-packages/rosdep-0.10.11-py2.7.egg/rosdep2/sources_list.py", line 497, in create_default
    matcher = DataSourceMatcher.create_default(os_override=os_override)
  File "/usr/local/lib/python2.7/dist-packages/rosdep-0.10.11-py2.7.egg/rosdep2/sources_list.py", line 229, in create_default
    os_name, os_version, os_codename = os_detect.detect_os()
  File "/usr/local/lib/python2.7/dist-packages/rospkg-1.0.17-py2.7.egg/rospkg/os_detect.py", line 405, in detect_os
    raise OsNotDetected("Could not detect OS, tried %s"%attempted)
OsNotDetected: Could not detect OS, tried ['ubuntu', 'rhel', 'osx', 'opensuse', 'mint', 'gentoo', 'freebsd', 'fedora', 'debian', 'cygwin', 'arch']