Comment 7 for bug 93947

Just to comment that I believe our goal is to actually copy across the revisions referenced by tags, so that they don't go completely dead.

That said, push --overwrite should be forcing the new values to be copied across, and if it isn't then this bug should be re-opened.

However, I just tested it now, and doing:

bzr init xtag
cd xtag
bzr commit -m one --unchanged
bzr commit -m two --unchanged
bzr commit -m three --unchanged
bzr tag -r 2 x
bzr push ../ytag
bzr tags -d ../ytag

x 2

bzr tag -r 3 x --force
bzr push ../ytag

No new revisions to push.
Conflicting tags:
    x

bzr tags -d ../ytag

x 2

bzr push --overwrite ../ytag

No new revisions to push.

bzr tags -d ../ytag

x 3

Admittedly this is with bzr.dev which is soon to become 1.10rc1. However, I believe this was fixed a while ago. It is possible it still fails with a remote branch, or over bzr+ssh, etc. We may want to open a new bug for that.

As for "I'm on 1.5.1 and 1.3.1" do you mean "1.5" and "1.3.1" as there was never a 1.5.1 release. Or maybe 1.6.1 ? Did you try "--overwrite"?