[Ros-release] Groovy package dependency updates

Daniel Stonier d.stonier at gmail.com
Thu Dec 20 02:31:49 UTC 2012 

On 20 December 2012 01:21, Vincent Rabaud <vrabaud at willowgarage.com> wrote:

> this macro is in actionlib_msgs. Please make sure you depend on it and
> that you have the latest version of the package.
>
>
ach, obvious...thanks. Somone slipped in an action into the stack without
me noticing it and I didn't pick up on it.

Daniel.


>
> On Wed, Dec 19, 2012 at 3:23 PM, Daniel Stonier <d.stonier at gmail.com>wrote:
>
>>
>>
>> On 17 December 2012 06:22, Tully Foote <tfoote at willowgarage.com> wrote:
>>
>>> Thanks to everyone's efforts we appear to have fixed almost all the wet
>>> packages.
>>>
>>> There are still several dry packages which are broken due to requiring
>>> the formerly leaked dependencies.  We're looking at adding those as
>>> dependencies for rosbuild so that no dry packages need to be updated for
>>> this cleanup.  (If you are releasing dry feel free to clean up the
>>> dependencies as stated above. )  With adding these dependencies back most
>>> packages should be building again in the next cycle or two.
>>>
>>> Tullly
>>>
>>>
>> Trying to release a 'dry' xxx_msgs package that was previously building,
>> albeit with the very non-specific 'ros' and 'ros_comm' as the dependencies
>> listed in stack.xml. You mentioned cleaning up the dependencies as stated
>> above...where exactly is above? ;) Previously you mentioned some
>> instructions for wet (ie dependencies for message_generation and
>> message_runtime), do these apply for dry as well? Not having much luck with
>> them set like that in the prereleases and with the old ros/ros_comm
>> dependency, I'm getting the following error at jenkins:
>>
>> [ rosmake ] Last 27 lines
>> {-------------------------------------------------------------------------------
>>   make[2]: Entering directory `/tmp/buildd/ros-groovy-kobuki-msgs-0.1.4/debian/ros-groovy-kobuki-msgs/opt/ros/groovy/stacks/kobuki_msgs'
>>   mkdir -p bin
>>   cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=/opt/ros/groovy/share/ros/core/rosbuild/rostoolchain.cmake  ..
>>   -- The C compiler identification is GNU
>>   -- The CXX compiler identification is GNU
>>   -- Check for working C compiler: /usr/lib/ccache/gcc
>>   -- Check for working C compiler: /usr/lib/ccache/gcc -- works
>>   -- Detecting C compiler ABI info
>>   -- Detecting C compiler ABI info - done
>>   -- Check for working CXX compiler: /usr/lib/ccache/c++
>>   -- Check for working CXX compiler: /usr/lib/ccache/c++ -- works
>>   -- Detecting CXX compiler ABI info
>>   -- Detecting CXX compiler ABI info - done
>>   -- Found PythonInterp: /usr/bin/python (found version "2.7.3")
>>   CMake Error at CMakeLists.txt:14 (include):
>>     include could not find load file:
>>
>>       /cmake/actionbuild.cmake
>>
>>
>>   CMake Error at CMakeLists.txt:15 (genaction):
>>     Unknown CMake command "genaction".
>>
>>
>>   -- Configuring incomplete, errors occurred!
>>   make[2]: *** [all] Error 1
>> -------------------------------------------------------------------------------}
>> [ rosmake ] Output from build of package kobuki_msgs written to:
>> [ rosmake ]    /tmp/.ros/rosmake/rosmake_output-20121219-103151/kobuki_msgs/build_output.log
>> [rosmake-0] Finished <<< kobuki_msgs [FAIL] [ 1.65 seconds ]
>>
>>
>> Thanks,
>>
>> Daniel.
>>
>>
>>
>>>
>>> On Sun, Dec 16, 2012 at 12:28 AM, Vincent Rabaud <
>>> vrabaud at willowgarage.com> wrote:
>>>
>>>> Indeed, a small tweak was needed because I did not follow the ROS
>>>> platform manager instructions.
>>>> Community, you should always follow the ROS platform manager
>>>> instructions :)
>>>>
>>>> Jack, camera1394 builds fine now.
>>>>
>>>>
>>>> On Sat, Dec 15, 2012 at 10:57 PM, Tully Foote <tfoote at willowgarage.com>wrote:
>>>>
>>>>> Hi Jack,
>>>>>
>>>>> If you click on the first box in each column it is a link to the
>>>>> debbuild jobs: for example oneiric 64 camera1394:
>>>>> http://jenkins.willowgarage.com:8080/view/GbinO64/job/ros-groovy-camera1394_binarydeb_oneiric_amd64/
>>>>> It looks like it's blocked by the package polled_camera:
>>>>> http://jenkins.willowgarage.com:8080/job/ros-groovy-polled-camera_binarydeb_oneiric_amd64/
>>>>> (look at the upstream jobs in the main job view for red dots) Which from
>>>>> the console output is missing a header file:
>>>>> http://jenkins.willowgarage.com:8080/job/ros-groovy-polled-camera_binarydeb_oneiric_amd64/45/console
>>>>> Which looks suspiciously like a message header file is not being generated.
>>>>>
>>>>>
>>>>> Vincent,
>>>>>
>>>>> From the above it looks like polled_camera needs a small tweak.
>>>>>
>>>>> Tully
>>>>>
>>>>>
>>>>> On Sat, Dec 15, 2012 at 8:57 AM, Jack O'Quin <jack.oquin at gmail.com>wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, Dec 15, 2012 at 10:15 AM, Jack O'Quin <jack.oquin at gmail.com>wrote:
>>>>>>
>>>>>>>
>>>>>>> On Sat, Dec 15, 2012 at 3:07 AM, Tully Foote <
>>>>>>> tfoote at willowgarage.com> wrote:
>>>>>>>
>>>>>>>> Hi everyone:
>>>>>>>>
>>>>>>>> We have cleaned up the dependencies of the core ros packages as a
>>>>>>>> result we don't leak dependencies downstream improperly.  This broke a
>>>>>>>> bunch of packages that relied on these leaked dependencies.
>>>>>>>>
>>>>>>>> We just did a hackathon to fix up most packages but we didn't have
>>>>>>>> time or access to fix all packages.  Please take a look at your packages if
>>>>>>>> you see that their build status is red on the build farm, hopefully the
>>>>>>>> error will be obvious.  If not please email us.  If it's gray, something
>>>>>>>> downstream is blocking it, and if it's yellow there's a warning, but it did
>>>>>>>> build successfuly.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Here's the summary of what we did for each package:
>>>>>>>>
>>>>>>>> 1) update package.xml to change build_depend(catkin) ->
>>>>>>>> buildtool_depend(catkin), or add buildtool_depend(catkin) if none was
>>>>>>>> specified.
>>>>>>>>
>>>>>>>> 2) Check if packages have warning on the buildfarm: either due to
>>>>>>>> invalid fields in package.xml or legacy setup.py style  The debbuild job
>>>>>>>> history will have yellow buttons, click on those will show warnings.
>>>>>>>>
>>>>>>>> 3) Remove dependencies on langs, genmsg and langs-dev in message
>>>>>>>> packages, they become build_depend on message_generation  and run_depend on
>>>>>>>> message_runtime.
>>>>>>>>
>>>>>>>> The farm is actively rebuilding groovy and we'll be turning it over
>>>>>>>> regularly.  If you have any questions please feel free to ask.
>>>>>>>>
>>>>>>>
>>>>>>> What about dry packages?
>>>>>>>
>>>>>>> According  to the status page [
>>>>>>> http://www.ros.org/debbuild/groovy.html], camera1394 1.8.0 is now
>>>>>>> broken (Red, Green, Green).
>>>>>>>
>>>>>>> Where do I look to figure out what went wrong?
>>>>>>>
>>>>>>> The old debbuild page looks like it was working 10 days ago: [
>>>>>>> http://build.willowgarage.com/view/All/job/devel_groovy_camera1394_precise_amd64/
>>>>>>> ]
>>>>>>>
>>>>>>> Is that information stored somewhere else now?
>>>>>>>
>>>>>>
>>>>>> I tried running a pre-release test for camera1394 on Groovy, but the
>>>>>> unit tests fail to run. That is nothing new. Unit tests fail for every dry
>>>>>> stack pre-release I have attempted on Groovy.
>>>>>>
>>>>>> There was some discussion a while back concerning libgtest. Has that
>>>>>> been resolved? Because of it, I have not been able to release any new (dry)
>>>>>> packages to Groovy.
>>>>>>
>>>>>> This seems like a critical problem. Is it already known? Should I
>>>>>> open a defect ticket?
>>>>>>  --
>>>>>>  joq
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Tully Foote
>>>>> tfoote at willowgarage.com
>>>>> (650) 475-2827
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Tully Foote
>>> tfoote at willowgarage.com
>>> (650) 475-2827
>>>
>>> _______________________________________________
>>> Ros-release mailing list
>>> Ros-release at code.ros.org
>>> https://code.ros.org/mailman/listinfo/ros-release
>>>
>>>
>>
>>
>> --
>> Phone : +82-10-5400-3296 (010-5400-3296)
>> Home: http://snorriheim.dnsdojo.com/
>> Yujin R&D: http://rnd.yujinrobot.com/
>>
>>
>> _______________________________________________
>> Ros-release mailing list
>> Ros-release at code.ros.org
>> https://code.ros.org/mailman/listinfo/ros-release
>>
>>
>


-- 
Phone : +82-10-5400-3296 (010-5400-3296)
Home: http://snorriheim.dnsdojo.com/
Yujin R&D: http://rnd.yujinrobot.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-release/attachments/20121220/92e73c74/attachment-0009.html>

More information about the Ros-release mailing list