[git-buildpackage] Tracking remote pristine-tar on salsa

[Agustin Henze]

Hi there, we (the salsa-ci-team) are trying to get a useful pipeline for Debian
Maintainers[0]. Right now we are using the following for building a package:

 - gbp pull --ignore-branch
 - gbp buildpackage --git-ignore-branch --git-export-dir=${WORKING_DIR} -us -uc

All seems to work fine (actually it does work), but we found that gbp is not
using the `pristine-tar` branch for building the orig tarball. Reading the doc,
I can see the recommended way is using gbp clone but here we don't have any
control over how Gitlab does the cloning. Is there a gbp friendly command to
track the remote pristine-tar branch after the repo was cloned using just `git
clone`?

Also, I'd like to take the advantage of this mail to ask for best practices
about how to build a Debian package using gbp inside salsa :). It'd be better
if you answer in another thread.

[0] https://salsa.debian.org/salsa-ci-team/pipeline/

-- 
TiN

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sigxcpu.org/pipermail/git-buildpackage/attachments/20180807/bc1690c4/attachment.sig>