Hi,
while working on maradns packaging, we observed (by having our package upload
rejected) that pristine-tar generates a tar.bz2 file that is slightly different
that
what was originally uploaded to pristine-tar.

Here is a relevant rejection text:

maradns_2.0.09-4.dsc: Invalid size hash for maradns_2.0.09.orig.tar.bz2:
According to the control file the size hash should be 1139409,
but maradns_2.0.09.orig.tar.bz2 has 1089174.

To reproduce please do:

  (1) wget
http://ftp.de.debian.org/debian/pool/main/m/maradns/maradns_2.0.09.orig.tar.bz2
  (2) git clone git://anonscm.debian.org/collab-maint/maradns.git
      cd maradns
      pristine-tar checkout maradns_2.0.09.orig.tar.bz2

You'll notice that the first file has 1089174 bytes, whereas the second 1139409
bytes. For all
we know, the tarballs created before were ok (3 uploads were made before). If
you uncompress these
2 files with bunzip2, you will see that both tars are identical, though.

There is a functionality proposed in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=608406
that would catch this in theory.

This problem has been workarounded by taking the orig tarball from the archive
and building against it.

Cheers,
Tomasz

Hi,
the problem with the tarball has been fixed by reuploading it to the
pristine-tar branch: http://anonscm.debian.org/cgit/collab-maint/maradns.git/log/?h=pristine-tar

I live this bug open nevertheless - I think there is an issue somewhere.

Tomasz