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

[Guido Günther]

Hi Agustin,
On Tue, Aug 21, 2018 at 09:46:06AM +0200, Agustin Henze wrote:
[..snip..]
> > The --git-pristine-tar-commit is for the case when a project does not
> > use pristine-tar.
> > 
> 
> Ah ok, still not getting your point, sorry... I've tried here with two
> repositories one with pristine-tar[0] and the other without it[1]. Both cases
> worked well or at least as I expected. The first one used the pristine-tar
> branch to build the orig.tarball and the second one used the upstream branch.
> 
> [0] https://salsa.debian.org/debian/lm4tools/-/jobs/40605
> $ gbp pull --ignore-branch --pristine-tar --track-missing
> gbp:info: Fetching from default remote for each branch
> gbp:info: Found detached head at '7ab08a9455da6e47798ffe3de841f124103c01d4'
> gbp:info: Branch 'upstream' is already up to date.
> gbp:info: Branch 'pristine-tar' is already up to date.
> gbp:info: Branch 'master' is already up to date.
> $ gbp buildpackage --git-ignore-branch --git-export-dir=${WORKING_DIR}
> --git-builder='docker-build.sh
> registry.salsa.debian.org/salsa-ci-team/images/dockerbuilder'
> gbp:info: Creating /builds/debian/lm4tools/debian/output/lm4tools_0.1.3.orig.tar.gz
> gbp:info: Exporting 'HEAD' to '/builds/debian/lm4tools/debian/output/lm4tools-tmp'
> 
> [1] https://salsa.debian.org/debian/crrcsim/-/jobs/40659
> $ gbp pull --ignore-branch --pristine-tar --track-missing
> gbp:info: Fetching from default remote for each branch
> gbp:info: Found detached head at '83bddfd3ea9962382112234c6e5bf465b0024ad0'
> gbp:info: Branch 'master' is already up to date.
> gbp:info: Branch 'upstream' is already up to date.
> $ gbp buildpackage --git-ignore-branch --git-export-dir=${WORKING_DIR}
> --git-builder='docker-build.sh
> registry.salsa.debian.org/salsa-ci-team/images/dockerbuilder'
> gbp:info: Creating crrcsim_0.9.13.orig.tar.gz from 'upstream/0.9.13'

This works but both builds will not be using pristine-tar, that's why I
proposed the pristine-tar commit (and the gbp export-orig modifications
as the long term fix). You can just ignore that for the moment and I'll
ping once I have the export-orig fixes in place.
Cheers,
 -- Guido