Issue 310 in rtm-ros-robotics: Release rtmros_common 1.0.6 into ROS

[rtm-ros-...@googlecode.com]

Status: Accepted
Owner: iisaac.s...@gmail.com
CC: kei.ok...@gmail.com
Labels: Type-Task Priority-Medium

New issue 310 by gm130s: Release rtmros_common 1.0.6 into ROS
http://code.google.com/p/rtm-ros-robotics/issues/detail?id=310

I'll do so today unless there's "no".

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[rtm-ros-...@googlecode.com]

Updates:
Status: Started

Comment #1 on issue 310 by gm130s: Release rtmros_common 1.0.6 into ROS
http://code.google.com/p/rtm-ros-robotics/issues/detail?id=310

Release stuck since the dependent package `pr2_controllers` [0] is dry in
groovy http://www.ros.org/debbuild/groovy.html?q=pr2_controllers.

It IS wet in hydro http://www.ros.org/debbuild/hydro.html?q=pr2_controllers.

[0]
http://code.google.com/p/rtm-ros-robotics/source/browse/trunk/rtmros_common/hrpsys_ros_bridge/package.xml?spec=svn6944&r=6944#34

[rtm-ros-...@googlecode.com]

Comment #2 on issue 310 by gm130s: Release rtmros_common 1.0.6 into ROS
http://code.google.com/p/rtm-ros-robotics/issues/detail?id=310

It builds locally with catkin_make, but not on prerelease[0], and with
bloom.

[0] Result on pre-release source build
http://jenkins.ros.org/job/prerelease-hydro-rtmros_common/ARCH_PARAM=amd64,UBUNTU_PARAM=precise,label=prerelease/1/consoleFull

Here's what bloom returns:

$ bloom-release --version
0.4.8
$ bloom-release --rosdistro groovy --track groovy rtmros_common
==> Fetching 'rtmros_common' repository
from 'https://github.com/start-jsk/rtmros_common-release.git'
Cloning into '/tmp/tmp4ZqMde'...
:
==> Testing for push permission on release repository
==> git remote -v
origin https://github.com/start-jsk/rtmros_common-release.git (fetch)
origin https://github.com/start-jsk/rtmros_common-release.git (push)
:
What version are you releasing (version should normally be
MAJOR.MINOR.PATCH)? 1.0.6

Executing release track 'groovy'
==> bloom-export-upstream
https://rtm-ros-robotics.googlecode.com/svn/tags/rtmros_common-1.0.6 svn
--tag :{none} --display-uri
https://rtm-ros-robotics.googlecode.com/svn/tags/rtmros_common-1.0.6 --name
upstream --output-dir /tmp/tmpmvVVgO
Checking out repository
at 'https://rtm-ros-robotics.googlecode.com/svn/tags/rtmros_common-1.0.6'.
A /tmp/P6q8cW/upstream/rosnode_rtc
:
A /tmp/P6q8cW/upstream/rtmros_common/CMakeLists.txt
Checked out revision 6946.
Exporting to archive: '/tmp/tmpmvVVgO/upstream.tar.gz'
md5: 83039aba96f0adbeca4f497e06cb6368

==> git-bloom-import-upstream /tmp/tmpmvVVgO/upstream.tar.gz
--release-version 1.0.6 --replace
The latest upstream tag in the release repository is 'upstream/1.0.5'.
Importing archive into upstream branch...
Creating tag: 'upstream/1.0.6'
I'm happy. You should be too.

==> git-bloom-generate -y rosrelease groovy --source upstream -i 0
Releasing packages:
['hrpsys_ros_bridge', 'openrtm_tools', 'hrpsys_tools', 'rtmros_common', 'rosnode_rtc', 'openrtm_ros_bridge', 'rtmbuild']
Releasing package 'hrpsys_ros_bridge' for 'groovy'
to: 'release/groovy/hrpsys_ros_bridge'
[git-bloom-patch import]: 'execute_command' failed to call 'git am
/tmp/tmp6XwrHR/*.patch' which had a return code (1):
[git-bloom-patch import]: ```
Applying: groovy does not have pr2_controllers package
error: patch failed: package.xml:22
error: package.xml: patch does not apply
Patch failed at 0001 groovy does not have pr2_controllers package
When you have resolved this problem run "git am --resolved".
If you would prefer to skip this patch, instead run "git am --skip".
To restore the original branch and stop patching run "git am --abort".

[git-bloom-patch import]: ```
[git-bloom-patch import]: Failed to apply one or more patches for
the 'Command 'git am /tmp/tmp6XwrHR/*.patch' returned non-zero exit status
1' branch.


>>> Resolve any conflicts and when you have resolved this problem
run 'git am --resolved' and then exit the shell using 'exit 0'. <<<
To abort use 'exit 1'
(bloom)exit
exit
[git-bloom-patch import]: User reports that conflicts have been
resolved, continuing.
[git-bloom-patch import]: Applied 1 patches
:
#### Generating 'precise' debian for package 'hrpsys_ros_bridge' at
version '1.0.6-0'
####
Generating debian for precise...
Could not resolve rosdep key 'pr2_controllers'
Try to resolve the problem with rosdep and then continue.
Continue [Y/n]?
Running 'rosdep update'...
Could not resolve rosdep key 'pr2_controllers'
Try to resolve the problem with rosdep and then continue.
Continue [Y/n]? n

[rtm-ros-...@googlecode.com]

Comment #3 on issue 310 by kei.ok...@gmail.com: Release rtmros_common 1.0.6
into ROS
http://code.google.com/p/rtm-ros-robotics/issues/detail?id=310

hope https://code.google.com/p/rtm-ros-robotics/issues/detail?id=260#c5
helps, that's what I did for 1.0.5

[rtm-ros-...@googlecode.com]

Comment #4 on issue 310 by gm130s: Release rtmros_common 1.0.6 into ROS
http://code.google.com/p/rtm-ros-robotics/issues/detail?id=310

Released into Hydro by normal steps.
https://github.com/ros/rosdistro/pull/3037

[rtm-ros-...@googlecode.com]

Updates:
Status: Duplicate

Comment #5 on issue 310 by iisaac.s...@gmail.com: Release rtmros_common

1.0.6 into ROS
http://code.google.com/p/rtm-ros-robotics/issues/detail?id=310

Moved to https://github.com/start-jsk/rtmros_common/issues/308