Hi Sébastien, Your suggestion was correct - I was not aware of the --git-pristine-tar option. I don't think I would have found that option myself.
I've pushed the history-rewritten changes, so the tag upstream/0.0.20 should now generate a byte-identical tarball. I've also re-tested this under cowbuilder. As an aside : Is there some discussion as to why this is an option, rather than the default? Hopefully this is right/usable now... On 15/10/17 14:46, Sébastien Villemot wrote: > Hi, > > On Sun, Oct 15, 2017 at 01:12:09PM +0100, D Haley wrote: > >> I rolled back history, and had to manually ssh in and hand edit the git >> repository on the remote, as pushing with --force is denied by the remote. >> [remote rejected] master->master (non fast-forward) >> >> I'm unable to get gbp to generate a byte-for-byte identical tarball, >> even if the contents are byte-for-byte identical when unpacked. I'm at a >> loss for what to do, as cloning the current repository >> >> $ gbp import-orig --pristine-tar ../3depict_0.0.20.orig.tar.gz >> What is the usptream version? [0.0.20] >> ... >> gbp:info Successfully imported version 0.0.20 of >> ../3depict_0.0.20.orig.tar.gz >> >> $ mv 3depict_0.0.20.orig.tar.gz 3depict_0.0.20.orig.tar.gz.real >> >> $ gbp buildpackage -S >> ... >> Ctrl+C >> >> $sha1sum *gz* >> <completely different SHA1 sums> > > It looks like you forgot to pass the --git-pristine-tar option to gbp > buildpackage. > >> Thanks, and apologies for taking up your time. > > No worry, I’m happy to help. > -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
