git-buildpackage should allow to use pristine-tar when there is
pristine tar entry for the current version. Often you need to
create a tarball on your own *and* you want to use pristine-tar
to make it more easy to rebuild the package with the same tarball,
without the need to download it from the archive.

Hi Bernd,
I don't understand this. You're able to use pristine-tar with
--pristine-tar.
Do you mean something like:

git-buildpackage --no-pristine-tar
git-import-orig --pristine-tar <created-orig-tarball>
# from then on
git-buildpackage --pristine-tar

Cheers,
 -- Guido

Hi Guido!

Guido Günther wrote:

Exactly. Only that I want to skip the manual steps and let git-bp handle it
automatically, probably as an toption so I can mess with my upstream branch and
don't get a new pristine-tar commit every time.

Cheers,

Bernd

Hmmm...I'm not sure I want to get gbp itself into this. So does this
look correct:

gbp-<whatever>:
* fetch new upstream tarball
* import it using git-import-orig to branch a

By-Hand:
* munge it

gbp-<whatever>:
* build a orig.tar.gz from branch a
* import it onto another branch b
* call pristine-tar on b

is that right?
 -- Guido