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)


On Fri, Jul 27, 2012 at 12:52 PM, Jack O'Quin <jack.oquin@gmail.com> wrote:
On Thu, Jul 26, 2012 at 6:43 PM, Tully Foote <tfoote@willowgarage.com> wrote:
> For the old style debs it's unfortunately cumbersome.  What you need to do
> is identify the rosdistro, distro, arch and find that job on
> build.willowgarage.com.  Ala
> http://build.willowgarage.com/job/debbuild-build-debs-fuerte-precise-i386/
> The job is parameterized.  It's either run with a specific stack name or ALL
> as a parameter.  You want to find the most recent ALL job that failed.  To
> find the parameter you need to click on a specific job instance: for example
> 470
> http://build.willowgarage.com/job/debbuild-build-debs-fuerte-precise-i386/470/
> and then click on the parameters button to show the parameters.  It shows
> ALL.  Then click on the [raw] button for the console output and find where
> it started building your package. ( A shortcut to finding the ALL builds is
> usually that they are red, when individual releases ususally are blue.  )
>
> If it's a compile failure you can look for [FAIL] but if it's a packaging
> issues unfortunately you need to search for the name of the stack.

Thanks for the pointer.

Looking at that one, about all I see is this (which does not tell
much). Where is the pbuilder output?

===================
[build_debs]: selecting [velodyne] because [ros-fuerte-velodyne,
0.9.1-\w*~precise] not in repo
[build_debs]: Attempting to build: ('velodyne', '0.9.1')
[build_debs]: Initiating build of: ('velodyne', '0.9.1')
[build_debs]: Actually trying to build velodyne-0.9.1...
[build_debs]: starting pbuilder build of velodyne-0.9.1
[build_debs]: Build of [('velodyne', '0.9.1')] failed, adding to broken list
[build_debs]: looking for next stack to build. Current deps list is
=======================

Before Fuerte, I was always able to solve problems like this using the
pre-release tests. Now they no longer seem to work.
--
 joq
_______________________________________________
Ros-release mailing list
Ros-release@code.ros.org
https://code.ros.org/mailman/listinfo/ros-release