Package: pristine-tar
Version: 1.33
Severity: wishlist
When git-buildpackage is doing its thing in a repo with no pristine-tar
branch but with several remote pristine-tar branches, an internal
pristine-tar checkout gives the following error.
pristine-tar: There's no local pristine-tar branch. Several remote
pristine-tar branches exist.
Run "git branch --track pristine-tar <remote>" to create a local
pristine-tar branch
c37c6f8c5322217cc5041bde8bade11d45f45830 refs/remotes/github/pristine-tar
c37c6f8c5322217cc5041bde8bade11d45f45830 refs/remotes/origin/pristine-tar
If there were only one remote pristine-tar branch, it would just use
that and everything would be fine. I wish it would realize when there
are several but they all point to the same commit, as above, and just go
ahead and use it.
