[Ros-release] how to troubleshoot broken debs?
Shaun Edwards
shaun.edwards at gmail.com
Thu Aug 2 13:59:40 UTC 2012
I think I may have tracked it down.
The version the deb is built from:
https://code.ros.org/svn/release/download/stacks/abb/abb-0.1.0/
does not match the tagged repo version:
<http://code.google.com/p/swri-ros-pkg/source/browse/#svn%2Ftags%2Fabb%2Fabb-0.1.0%253Fstate%253Dclosed>
http://code.google.com/p/swri-ros-pkg/source/browse/#svn%2Ftags%2Fabb%2Fabb-0.1.0
This file is the problem:
http://code.google.com/p/swri-ros-pkg/source/browse/tags/abb/fuerte/abb_common/CMakeLists.txt
I've tried to fix the release by using:
rosrelease-legacy abb 0.1.0 fuerte
It's probably something I am doing, but how to I overwrite the deb version
in ros release? Maybe I can't. Maybe I need to release a new version
number?
-Shaun
On Wed, Aug 1, 2012 at 2:17 PM, Vincent Rabaud <vrabaud at willowgarage.com>wrote:
> Just trigger an individual build and checkout the error message:
>
> http://build.willowgarage.com/job/debbuild-build-debs-fuerte-lucid-i386/1017/console
>
> You need to re-release after you remove the xacro dependency
>
>
> On Wed, Aug 1, 2012 at 9: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?
>>
>> On Fri, Jul 27, 2012 at 4:10 PM, Jack O'Quin <jack.oquin at gmail.com>wrote:
>>
>>> On Fri, Jul 27, 2012 at 3:24 PM, Vincent Rabaud
>>> <vrabaud at willowgarage.com> wrote:
>>> > Here is how to debug it (I know, it is not trivial)
>>> >
>>> > Look for a few lines above when it is trying to build it:
>>> >
>>> > The following packages have unmet dependencies:
>>> > pbuilder-satisfydepends-dummy : Depends: yaml-cpp0.2.6-dev which is a
>>> > virtual package.
>>> > Depends: libpcap0.8-dev but it is not
>>> going
>>> > to be installed.
>>> > Depends: ros-fuerte-common-msgs but
>>> it is
>>> > not going to be installed.
>>> > Depends: ros-fuerte-diagnostics but
>>> it is
>>> > not going to be installed.
>>> > Depends: ros-fuerte-geometry but it
>>> is not
>>> > going to be installed.
>>> > Depends: ros-fuerte-nodelet-core but
>>> it is
>>> > not going to be installed.
>>> > Depends: ros-fuerte-perception-pcl
>>> but it
>>> > is not going to be installed.
>>> > Depends: ros-fuerte-ros but it is not
>>> going
>>> > to be installed.
>>> > Depends: ros-fuerte-ros-comm but it
>>> is not
>>> > going to be installed.
>>> > The following actions will resolve these dependencies:
>>> >
>>> > Remove the following packages:
>>> > 1) pbuilder-satisfydepends-dummy
>>> >
>>> >
>>> >
>>> > The following packages will be REMOVED:
>>> > pbuilder-satisfydepends-dummy{a}
>>> > 0 packages upgraded, 0 newly installed, 1 to remove and 31 not
>>> upgraded.
>>> >
>>> >
>>> > So it basically means that it is trying to install yaml-cpp0.2.6-dev.
>>> If you
>>> > look at your yaml file:
>>> >
>>> https://code.ros.org/svn/release/download/stacks/velodyne/velodyne-0.9.1/velodyne-0.9.1.yaml
>>> > (that you can access by clicking on velodyne from
>>> > http://www.ros.org/debbuild/fuerte.html ) it indeed contains that for
>>> > precise.
>>> >
>>> > Now, if you look at that file:
>>> > https://github.com/ros/rosdistro/blob/master/rosdep/base.yaml
>>> > you can see that the yaml-cpp dependency for precise, it is called
>>> yaml-cpp
>>> > and not yaml-cpp0.2.6-dev
>>> >
>>> > So when generating your yaml file, there basically was the wrong
>>> dependency
>>> > exported for precise. That means you had not done 'rosdep update'
>>> before
>>> > releasing. That's it !
>>> >
>>> >
>>> > And pre-release should still work for dry stuff (used it last week)
>>>
>>> Thanks a lot, Vincent!
>>>
>>> I got bit by that once before, because I had previously updated a
>>> clone of the rosdistro rosdep repo and that (by then out-of-date)
>>> version was still in my search path.
>>>
>>> That mistake is easy to make and really tough to find.
>>>
>>> I really appreciate the help.
>>> --
>>> joq
>>>
>>> _______________________________________________
>>> Ros-release mailing list
>>> Ros-release at code.ros.org
>>> https://code.ros.org/mailman/listinfo/ros-release
>>>
>>
>>
>> _______________________________________________
>> Ros-release mailing list
>> Ros-release at code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-release
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-release/attachments/20120802/14a2b520/attachment-0009.html>
More information about the Ros-release
mailing list