I just re-triggered a build and it was successful again for orocos_toolchain. Anyway, the debs are there: http://packages.ros.org/ros/ubuntu/pool/main/r/ros-fuerte-orocos-toolchain/ http://50.28.27.175/repos/building/pool/main/r/ros-fuerte-orocos-toolchain/ I don't get why the build farm does not find it either: http://jenkins.willowgarage.com:8080/job/ros-fuerte-rtt-ros-integration_binarydeb_oneiric_i386/18/console Tully ? On Wed, Dec 19, 2012 at 11:44 AM, Peter Soetens wrote: > On Wed, Dec 19, 2012 at 11:17 AM, Ruben Smits > wrote: > > Hi, > > > > Some time ago I released rtt_ros_integration, rtt_ros_comm, > > rtt_common_mgs for Fuerte. The debs however are still not availabe. I > > tracked this down to rtt_ros_integration not being build due to the > > missing dependency of the orocos_toolchain: > > > > + cat > > + '[' rtt_ros_integration == metapackages ']' > > + bash > /home/rosbuild/hudson/workspace/ros-fuerte-rtt-ros-integration_binarydeb_precise_amd64/build.bash > > [rtt_ros_integration] ignoring dependency [common_msgs], possible > catkin-ized > > [orocos_toolchain] ignoring dependency [ros], possible catkin-ized > > [rtt_ros_integration] ignoring dependency [ros_comm], possible > catkin-ized > > [build_debs]: loading distro file from > > https://code.ros.org/svn/release/trunk/distros/fuerte.rosdistro > > [build_debs]: Attempting to build: rtt_ros_integration > > [build_debs]: Skipping rtt_ros_integration (2.6.0-0) since > > dependencies not built: set(['ros-fuerte-orocos-toolchain']) > > [build_debs]: FAILURE: None > > > > orocos-toolchain however is already successfully released including > > debs for Fuerte, so I do not understand why the rtt_* debs are not > > being build. > > > > Can anyone shed a light on this? > > Would it help to trigger a build if we just re-released orocos-toolchain > again ? > > Peter > _______________________________________________ > Ros-release mailing list > Ros-release@code.ros.org > https://code.ros.org/mailman/listinfo/ros-release >