Re: GitLab CI failure question

[Julian Gilbey <julian@d-and-j.net>]

On Thu, Aug 23, 2018 at 12:38:20AM +0800, Shengjing Zhu wrote:
> On Wed, Aug 22, 2018 at 11:54 PM Julian Gilbey <julian@d-and-j.net> wrote:
> >
> > Hello!
> >
> > This is the first time I've committed something to salsa and the CI
> > has failed :-(
> >
> > I really don't understand why this would be.  The error message is
> > that the original tarball doesn't exist, but it builds perfectly well
> > on my own machine; gbp creates the tarball from the pristine-tar and
> > upstream branches.
> >
> > The package under question is:
> > https://salsa.debian.org/go-team/packages/golang-github-hanwen-go-fuse/
> >
> > Help much appreciated!
> 
> The failed command is `GBP_CONF_FILES=:debian/gbp.conf gbp
> buildpackage --git-no-pristine-tar --git-ignore-branch
> --git-ignore-new --git-export-dir=/tmp/export --git-no-overlay
> --git-tarball-dir=/nonexistant --git-cleaner=/bin/true
> --git-builder='dpkg-buildpackage -S -d --no-sign'`
> 
> So, from the params, you can find `--git-no-pristine-tar`. It won't
> use pristine-tar. As a result, gbp will create origtarball from
> upstream tag, which should be `upstream/0.0_git20180807.0.95c6370`.
> 
> The solution is to push the `upstream/0.0_git20180807.0.95c6370` tag.

Oh, how obvious!

Many thanks,

   Julian