It's perfectly find and expected for stacks to depend on ros. All stacks should depend on ros which are using anything from inside the ros stack, which is everything using rosbuild. This looks like a bug in the devel build scripts. Ticketed here: https://github.com/ros-infrastructure/jenkins_scripts/issues/5 Tully On Thu, Jan 31, 2013 at 7:05 AM, Jack O'Quin wrote: > > > On Thu, Jan 31, 2013 at 6:45 AM, Peter Soetens wrote: > >> It appears that if we depend on 'ros' in our stack.xml, the 'devel' >> build is not done due to this message: >> >> >> devel_fuerte_orocos_toolchain_precise_amd64 - Build # 16 - Fixed: >> >> Check console output at >> >> http://build.willowgarage.com//job/devel_fuerte_orocos_toolchain_precise_amd64/16/ >> to view the results. >> >> Result: Not all dependencies of stack orocos_toolchain have a Debian >> package. Skipping this devel build >> >> >> >> It tries to install ros-fuerte-ros, sees it's already there and then >> skips the build instead of proceeding... >> >> Can I just remove the dependency ? Will this not break other builds >> that do rely on it ? >> > > I have been wondering about this, too. I see various messages complaining > about things depending on "ros". > > Is it deprecated? When was it removed? What replaced it? > -- > joq > _______________________________________________ > Ros-release mailing list > Ros-release@code.ros.org > https://code.ros.org/mailman/listinfo/ros-release > > -- Tully Foote tfoote@willowgarage.com (650) 475-2827