On Fri, Mar 1, 2013 at 8:40 AM, Jack O'Quin wrote: > On Fri, Mar 1, 2013 at 3:39 AM, Tully Foote wrote: >> >> I'm not sure what's going on here. In groovy you will get that error if a dependency which is supposed to be a ros package doesn't exist on your path. The tools will then assume it must be a rosdep if it's not an existing package. I'll look into it tomorrow. I think it might be that the prerelease is installing the union of build and run depends, skipping the test_depends. If that's true, then rostest won't be installed, if that's how it should be will take a trip to the white board with some sketching to answer. > > That groovy-devel branch of camera1394 on github now has a package="rostest" />. I would not expect that to be interpreted as a > test_depends. > > https://github.com/ros-drivers/camera1394/blob/groovy-devel/manifest.xml > > Is there some other than "ros" needed in the stack.xml for > rostest to be accessible? Looks like the "ros" stack dependency no longer works. I added , and the pre-release tests seem to work now. That must be why rostest was not getting installed. If the tests all succeed, I will release camera1394-1.8.1 to Groovy soon. Is the stack dependency on "ros" even needed these days? Without rosstack, it's hard to figure out the correct dependencies for dry stacks. -- joq