Ask Your Question

bloom - same version number, different tag

asked 2019-02-13 10:40:27 -0500

David Lu gravatar image

I am trying to re-release robot_navigation. I have already bloomed the latest version (0.2.5) for lunar off of the master branch of the repo.

Melodic however uses the tf2 branch of the repo. I did catkin_prepare_release -t tf2 which created the tf20.2.5 (not my best choice of prefix, I'll admit). I also edited the release tag when doing bloom-release to be tf2:{version}.

However, when it attempts to push the tags to the release repository it fails.

==> Pushing tags to release repository for 'robot_navigation'
==> git push --tags
Total 0 (delta 0), reused 0 (delta 0)
 * [new tag]         debian/ros-melodic-costmap-queue_0.2.5-0_bionic -> debian/ros-melodic-costmap-queue_0.2.5-0_bionic
 * [new tag]         rpm/ros-melodic-robot-navigation-0.2.5-0_28 -> rpm/ros-melodic-robot-navigation-0.2.5-0_28
 ! [rejected]        upstream/0.2.5 -> upstream/0.2.5 (already exists)
error: failed to push some refs to ''
hint: Updates were rejected because the tag already exists in the remote.

This is presumably because I already pushed the tags with lunar.

What setting do I change to get it to use a different tag here?

(Previously, I used two separate version numbers for the two branches....lunar with 0.2.2 and melodic was 0.2.3...and 0.2.4)

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2019-02-14 14:08:52 -0500

nuclearsandwich gravatar image

Hmm. It looks like bloom's release tags don't use the full tag template when creating additional release tags. I believe that change would require a patch to implement and I haven't even begun to consider the side effects of such a change.

I think the two options for expedient resolution would be to use a different version number for the melodic track, which makes sense to me if the sources are divergent; or to use a different release repository so that the tags don't collide.

edit flag offensive delete link more


That works for me. Just wanted to make sure I wasn't missing an obvious option.

David Lu gravatar image David Lu  ( 2019-02-14 14:28:26 -0500 )edit

Just came here to say, if the content of the source is different, then the version number _must_ be different or the package name needs to change. Anything else leads to chaos in my opinion.

William gravatar image William  ( 2019-02-14 14:28:38 -0500 )edit

So what makes the most sense? I have two versions of this package that I plan to keep updating. I could keep leapfrogging odds/evens....

David Lu gravatar image David Lu  ( 2019-02-14 14:32:24 -0500 )edit

Most of the ROS 2 packages that are ported up have given themselves a bunch of version headroom. geometry2 comes to mind, the ros1 release is on 0.6.5 and is at 0.10.1 for ROS 2. If they'll both be supported, perhaps create a new package?

nuclearsandwich gravatar image nuclearsandwich  ( 2019-02-15 10:08:15 -0500 )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



Asked: 2019-02-13 10:40:27 -0500

Seen: 71 times

Last updated: Feb 14 '19