[git-buildpackage] Unexpected behaviour when upstream uses export-subst gitattribute

[Danny Edel]

On 28/08/15 17:13, Guido Günther wrote:
> 
> You're very likely not telling gbp how upstream tags look like using the
> --git-upstream-tag option our the upstream tarball isn't exactly
> generated from this tag.


Hello Guido,

thanks for the fast reply, but in this case I'm pretty sure that is not
the problem:

I did specify the upstream-tag-format in debian/gbp.conf¹, and gbp
buildpackage finds it. Since my pretend-upstream doesn't create
tarballs, gbp automagically builds one for me, and if I inspect this
.orig.tar.gz tarball, it contains the "hello" file with the upstream sha
"d2b818..." embedded, so it's actually built exactly from that version.

In ../build-dir/hello-world-version-1.0/hello (left there after the
build fails), is embedded the debian-packaging SHA, "63953...").

I used the export-dir option to have a directory with all the build
artifacts in one place, but without it the result is the same. I
basically followed the "No upstream tarballs" manual² to the step where
it says "git buildpackage" for the first time and there it fails on the
export-subst.

If cloning and "gbp buildpackage'ing" my minimal package repo works for
you, please tell me which version you use. I'm currently on debian/sid
with 0.6.32.
(Note that gbp buildpackage -b goes through without problems, it fails
when called without parameters or saying -S explicitly)

Thank you again,

- Danny

¹
https://github.com/dannyedel/pkg-hello-world-version/blob/debian/sid/debian/gbp.conf

²
http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.UPSTREAM.GIT.NOTARBALL