On Sat, Jun 27, 2015 at 01:46:21PM +0530, Balasankar C wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > Hi, > I am not sure that I understood completely, but please see inline. > On ശനി 27 ജൂണ് 2015 01:32 വൈകു, Cédric Boutillier wrote: > > The problem you have is that the upstream tarball you are using is > > not (strictly) the same as the one in the Debian archive. This is > > probably because by default, git-buildpackage does not use the > > pristine-tar branch to regenerate the upstream tarball if it > > doesn't find it, but generate it from scratch from the tag in the > > upstream branch. > Ok. So I don't really have anything to do with it (as I am not the > uploader, but my sponsor is; and he/she does the gbp buildpackage). Correct. > > It may happen also that the tarball in the pristine-tar branch is > > not the one in the archive. > This is caused because the initial upload to Debian archive consisted > an orig.tar.gz file that was not generated from the pristine-tar > branch (as mentioned in your first point). Right? Yes. > > Then you need to download manually the tarball from Debian archive. > > In that case, please commit the correct tarball in the pristine-tar > > branch with: pristine-tar commit <package.orig.tar.gz> and push the > > pristine-branch to the team repo. > Ok, I'll do that. Ok :) Cheers, Cédric
Attachment:
signature.asc
Description: Digital signature