All,<br><br>I think I am having a similar problem to Jack with my abb stack release.<br><br>My build fails on all archs ( ex:<a href="http://build.willowgarage.com/job/debbuild-build-debs-fuerte-precise-i386/489/console"> http://build.willowgarage.com/job/debbuild-build-debs-fuerte-precise-i386/489/console</a>)<br>
<br><snip><br><br><pre> make[2]: Entering directory `/tmp/buildd/ros-fuerte-abb-0.1.0/debian/ros-fuerte-abb/opt/ros/fuerte/stacks/abb/abb_common'
mkdir -p bin
cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=`rospack find rosbuild`/rostoolchain.cmake ..
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Found PythonInterp: /usr/bin/python (found version "2.7.3")
[rosbuild] Building package abb_common
Failed to invoke /opt/ros/fuerte/bin/rospack deps-manifests abb_common
[rospack] Error: package/stack abb_common depends on non-existent package xacro<br><br></pre><snip><br><br>I've removed the dependency on xacro from the stack manifest file (it's not needed), but it still fails.<br>
<br>I tried running 'rosdep update' from my local abb stack and then perform the release. It still fails.<br><br>Any suggestions?<br><br><div class="gmail_quote">On Fri, Jul 27, 2012 at 4:10 PM, Jack O'Quin <span dir="ltr"><<a href="mailto:jack.oquin@gmail.com" target="_blank">jack.oquin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Fri, Jul 27, 2012 at 3:24 PM, Vincent Rabaud<br>
<<a href="mailto:vrabaud@willowgarage.com">vrabaud@willowgarage.com</a>> wrote:<br>
> Here is how to debug it (I know, it is not trivial)<br>
><br>
> Look for a few lines above when it is trying to build it:<br>
><br>
> The following packages have unmet dependencies:<br>
> pbuilder-satisfydepends-dummy : Depends: yaml-cpp0.2.6-dev which is a<br>
> virtual package.<br>
> Depends: libpcap0.8-dev but it is not going<br>
> to be installed.<br>
> Depends: ros-fuerte-common-msgs but it is<br>
> not going to be installed.<br>
> Depends: ros-fuerte-diagnostics but it is<br>
> not going to be installed.<br>
> Depends: ros-fuerte-geometry but it is not<br>
> going to be installed.<br>
> Depends: ros-fuerte-nodelet-core but it is<br>
> not going to be installed.<br>
> Depends: ros-fuerte-perception-pcl but it<br>
> is not going to be installed.<br>
> Depends: ros-fuerte-ros but it is not going<br>
> to be installed.<br>
> Depends: ros-fuerte-ros-comm but it is not<br>
> going to be installed.<br>
> The following actions will resolve these dependencies:<br>
><br>
> Remove the following packages:<br>
> 1) pbuilder-satisfydepends-dummy<br>
><br>
><br>
><br>
> The following packages will be REMOVED:<br>
> pbuilder-satisfydepends-dummy{a}<br>
> 0 packages upgraded, 0 newly installed, 1 to remove and 31 not upgraded.<br>
><br>
><br>
> So it basically means that it is trying to install yaml-cpp0.2.6-dev. If you<br>
> look at your yaml file:<br>
> <a href="https://code.ros.org/svn/release/download/stacks/velodyne/velodyne-0.9.1/velodyne-0.9.1.yaml" target="_blank">https://code.ros.org/svn/release/download/stacks/velodyne/velodyne-0.9.1/velodyne-0.9.1.yaml</a><br>
> (that you can access by clicking on velodyne from<br>
> <a href="http://www.ros.org/debbuild/fuerte.html" target="_blank">http://www.ros.org/debbuild/fuerte.html</a> ) it indeed contains that for<br>
> precise.<br>
><br>
> Now, if you look at that file:<br>
> <a href="https://github.com/ros/rosdistro/blob/master/rosdep/base.yaml" target="_blank">https://github.com/ros/rosdistro/blob/master/rosdep/base.yaml</a><br>
> you can see that the yaml-cpp dependency for precise, it is called yaml-cpp<br>
> and not yaml-cpp0.2.6-dev<br>
><br>
> So when generating your yaml file, there basically was the wrong dependency<br>
> exported for precise. That means you had not done 'rosdep update' before<br>
> releasing. That's it !<br>
><br>
><br>
> And pre-release should still work for dry stuff (used it last week)<br>
<br>
</div></div>Thanks a lot, Vincent!<br>
<br>
I got bit by that once before, because I had previously updated a<br>
clone of the rosdistro rosdep repo and that (by then out-of-date)<br>
version was still in my search path.<br>
<br>
That mistake is easy to make and really tough to find.<br>
<br>
I really appreciate the help.<br>
<div class="HOEnZb"><div class="h5">--<br>
joq<br>
_______________________________________________<br>
Ros-release mailing list<br>
<a href="mailto:Ros-release@code.ros.org">Ros-release@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-release" target="_blank">https://code.ros.org/mailman/listinfo/ros-release</a><br>
</div></div></blockquote></div><br>