Ask Your Question
0

bloom pulls in older tagged version

asked 2016-05-18 15:02:00 -0600

130s gravatar image

updated 2018-11-01 05:59:48 -0600

While I'm making a release using bloom I noticed on the commandline that it pulled in an older tagged version. Why is that, and how can I make a release with the newest tagged version?

I manually made a release "0.8.0" on moveit_core github website (I thought I had to manually do so without using catkin_prepare_release, only because I had to increment from 0.6.15 to 0.8.0 for jade, which I had no idea how to achieve(*1)). But bloom wants to use 0.7.1, which is one older tag (and should be used for indigo but not for jade).

Not sure how related this is but looking at the list of releases page, comparing with other repositories where the latest tag I made by catkin_prepare_release, I noticed that the one I made manually (0.8.0 on moveit_core) seems highlighted, while in other repositories they look the same as older tags.


UPDATE *1 catkin_prepare_release has an option to allow specifying the new versions e.g. --bump or --version. See its help doc by -h.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2016-05-18 15:08:35 -0600

ahendrix gravatar image

Is your track configuration in bloom set to the correct branch?

edit flag offensive delete link more

Comments

You're right; it was pointing to a wrong branch and now it starts working as expected after I corrected with --edit option of bloom.

130s gravatar image130s ( 2016-05-18 15:27:27 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2016-05-18 15:02:00 -0600

Seen: 54 times

Last updated: Nov 01 '18