[Ros-release] how to troubleshoot broken debs?

[Jack O'Quin]

On Wed, Aug 1, 2012 at 11:05 AM, Shaun Edwards <shaun.edwards at gmail.com> wrote:
> All,
>
> I think I am having a similar problem to Jack with my abb stack release.
>
> My build fails on all archs ( ex:
> http://build.willowgarage.com/job/debbuild-build-debs-fuerte-precise-i386/489/console)
>
> <snip>
>
>   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
>
> <snip>
>
> I've removed the dependency on xacro from the stack manifest file (it's not
> needed), but it still fails.
>
> I tried running 'rosdep update' from my local abb stack and then perform the
> release.  It still fails.
>
> Any suggestions?

Do you have any local rosdep YAML test versions in your
/etc/ros/rosdep/sources.list.d directory?

That was the mistake I made (twice).
-- 
 joq