-----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). > 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? > 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. - -- Regards Balasankar C http://balasankarc.in -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBCgAGBQJVjlvUAAoJEJbtq5sua3Fx8qEH/iWSauz6A0b7O2BW//0uiUwj YzzFuvqg073JiugWcjfwz0vxn0pysEfRTnToU5qy4WexVgvMI7L2KglW6O4GW4Xu jEM24zBzDOHSeaQSbmbSrCtXdtQoNza8e13M0jNFYN6/xjYWCT6RuoULENkvmxOo WlBimoCWL4ebsOBfGaajN5KPWegme3sr68FeOOzc8rJKdpnsOR1Y+84k3vtHa6jS HHYCEUFQhx7GtX1KDJfuvf4RHesMUUfg1zbxQ+LghWBYQTtuItFrWW4K08TvIG57 bCNksmRWNULtUz72NLHtRmUMPzL9DpVmtg7CQzt+Q+nZJpZ6+fhHAieT2gFPPno= =HGvZ -----END PGP SIGNATURE-----
Attachment:
0x2E6B7171.asc
Description: application/pgp-keys