Closed 130s closed 10 years ago
Done in rosdistro.
sorry, we need to check this patch --> https://github.com/start-jsk/openhrp3/pull/23
Pre-release testing from "source" (not from release repo
, which means this should be presumable grabbing the latest source) failed, at downstream build test of hrpsys
.
Check if /tmp/test_repositories/build_repository/devel/share/openhrp3/share/OpenHRP-3.1/idl/OpenHRP/ClockGenerator.idl exists
CMake Error at idl/CMakeLists.txt:120 (message):
ERROR:
/tmp/test_repositories/build_repository/devel/share/openhrp3/share/OpenHRP-3.1/idl/OpenHRP/ClockGenerator.idl
is not present
-- Configuring incomplete, errors occurred!
make: *** [installed] Error 1
CMake Error at hrpsys/catkin.cmake:25 (message):
Compile hrpsys failed
Call Stack (most recent call first):
hrpsys/CMakeLists.txt:2 (include)
But looks like ClockGenerator.idl
is installed.
-- Installing: /tmp/test_repositories/build_repository/devel/share/OpenHRP-3.1/idl/OpenHRP/ClockGenerator.idl
So at this point we could make a judgement call to re-release OpenHRP3
package (by incrementing build version again).
@k-okada if you could confirm that there won't be update, I'll release this again. If there are still work ongoing I'll just wait.
On my local environment, it seems ok
Ok then I'll increment now
Done. We'll see how this goes...
Needs redone maybe because of https://github.com/start-jsk/openrtm_aist_core/issues/23
Once openrtm_aist_core
builds on Groovy, I'll re-release OpenHRP3
into Groovy, and Hydro.
OpenHRP3 builds fine with the updated openrtm_aist_core 1.1.0-4
.
Still, I assume OpenHRP3 needs to be re-released for this commit to be applied? @k-okada
I just re-released OpenHRP3 3.1.5-5
into Groovy -- it was an old 3.1.5-3
and thus hrpsys
didn't build on pre-release. Closing.
To apply this commit to ROS
.deb
.Just wanted to raise an attention: To release .deb by only incrementing build version (
MAJOR.MINOR.PATCH-BUILD
) is NOT allowed in ROS. So this must not happen often.I share how to do this JUST IN CASE it's needed in the future by someone else.
release tag
on your upstream repository. Do not use automation tools from ROS (eg.catkin_prepare_release
,catkin_generate_changelogs
). If the same tag already exists, you might want to remove it first and then push again with your new data that you're releasing this time.bloom-release
. Process normally, push the artifact that's built by bloom to your release repository. Open a pull request (bloom
will ask you to do so) to modifyrosdistro
with the newbuild version
.build version
. Sincerosdistro
maintainers are very careful with every detail, you have to give sufficient reasoning.