Comment 4 for bug 494481

This same traceback seems to sometimes happen when using merge-package to merge a new release from Debian. Take a look at lp:ubuntu/bzr-gtk It looks to me like I did every thing right (though it was a long time ago now). I merge in revision 13.2.8 revid:<email address hidden> which was a new upstream release
committed by Bazaar Package Importer <email address hidden> to the Debian branch, but the importer has been failing with "bzrlib.errors.NoSuchTag: No such tag: upstream-0.98.0" That's the version the importer itself pulled in...

If I go back in and manually push that tag will it make the branch usable? I just did a merge of bzr-gtk, and found it ironic that I had to use grab-merge.