Performing this operation results in an Error: "Tag release-1.0 already exists". However, after that I am able to checkout the tag directly using the previous command. bzr checkout -r tag:release-1.0 ftp://[domain]/[project]/trunk<div id=":2ek" class="ArwC7c ckChnd"> </div> So it seems the error is generated, but the tag is still pushed to the central repo. I am filing a bug with the aforementioned information. Thank you, Eric <div class="gmail_quote">On Fri, Jan 23, 2009 at 4:02 PM, Martin Pool <<a href="mailto:mbp@sourcefrog.net">mbp@sourcefrog.net</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">2009/1/23 Eric Berry <<a href="mailto:elberry@gmail.com">elberry@gmail.com</a>>: <div class="Ih2E3d">> Is there a way to push the unbounded tag to the central repo after my local > branch has been rebound? </div>It's probably a bug that it does not check them when you rebind (you could file one, or look for one, in the tracker.) As a workaround use bzr tags to find where it's bound and then just  bzr tag -r REVID -d sftp://....  TAGNAME -- Martin <<a href="http://launchpad.net/%7Embp/" target="_blank">http://launchpad.net/~mbp/</a>> </blockquote></div> -- Learn from the past. Live in the present. Plan for the future. 11101000 <a href="http://www.townsfolkdesigns.com/blogs/elberry">http://www.townsfolkdesigns.com/blogs/elberry</a>