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

Guido G√ľnther agx at sigxcpu.org
Tue Aug 7 21:53:34 CEST 2018


Hi,
On Tue, Aug 07, 2018 at 07:06:18PM +0200, Agustin Henze wrote:
> 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`?

In gitlab-ci this would be somthing like

   script:
      - git fetch origin pristine-tar
      - git branch pristine-tar FETCH_HEAD

or did I misunderstand your question?
Cheers,
 -- Guido

> 
> 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
> 




> _______________________________________________
> git-buildpackage mailing list
> git-buildpackage at lists.sigxcpu.org
> http://lists.sigxcpu.org/mailman/listinfo/git-buildpackage



More information about the git-buildpackage mailing list