Hi, I ran into this same issue today:
± git-debpush --gbp git-debpush: found upstream tags: v0.1.0 upstream/0.1.0 git-debpush: use --upstream=TAG to say which one to use Based on Ian's reply to Simon, the "upstream tag" that git-debpush/git-deborig is looking for is the tag git-buildpackage put on the commit that represents the upstream import. I support the idea here of reading the gbp.conf. Basically if --gbp is given to git-debpush, it could pass --gbp along to git-deborig, which could understand it should check debian/gbp.conf:upstream-branch and based on it pick the same tag git-buildpackage would use, in this case 'upstream/0.1.0'. Thanks for working on this gbp-compatibility feature. In the meanwhile I will just manually run: ± git-debpush --gbp --upstream=upstream/0.1.0 PS. This bug also discusses pristine-tar support. That is now in progress via Bug#1106071 in case other people who read this bug report were not aware of it.
