Hi, I also ran into this today when uploading a -2 version: git-debpush started to ask about the upstream tag and didn't automatically detect it based on what the -1 tag poitns to nor did it use the git-buildpackage default (`upstream/%s`) as discussed in Bug#1105759:
± git-debpush --gbp git-debpush: found upstream tags: v1.4.5 upstream/1.4.5 git-debpush: use --upstream=TAG to say which one to use I solved this by telling it manually to use `upstream/%s`: ± git-debpush --gbp --upstream=upstream/1.4.5 git-debpush: checking state at [email protected]:games-team/libbncsutil.git git-debpush: making signed tag debian/1.4.5-2 git-debpush: pushing to git remote origin It would of course be nice if it was automatic.
