fresh-releases and fresh-snapshots create conflicting upstream tarballs

I just noticed a failed upload of python-minikerberos_0.2.10-1jan+nus1_source.changes (thus built by fresh-snapshots) because the python-minikerberos_0.2.10.orig.tar.gz file it contained was not the same than the orig.tar.gz that was uploaded earlier as part of the fresh-releases job (0.2.10-1jan+nur1).

See http://pkg.kali.org/news/445758/accepted-python-minikerberos-0210-1jannur1-source-into-kali-experimental/ for the pre-existing fresh-releases upload.

And this failed upload:

It looks like the upload of python-minikerberos_0.2.10-1~jan+nus1_source.changes has not been
accepted by
reprepro. The last lines of /srv/repo.kali.org/logs/incoming.log
might help you:
File "pool/main/p/python-minikerberos/python-minikerberos_0.2.10.orig.tar.gz" is already
registered with different checksums!
md5 expected: 288f39f629f30c26231ddbe601032be3, got: a958bfade881b285c4885d39d53fbb7e
sha1 expected: 98fd77350ecaab0d7e32d5bee0d73d1f7c2ab44e, got:
12645d8ba63f7eda55ca0563aa409657c0b1b453
sha256 expected: 60d126b95f0e8ddb7996691082baeec4fcef20254d51bff6b849f7afe32b93f0, got:
b919e6cf00e52363fc4cede5852cef07d785bdb728f120b4465b54a64b313097
size expected: 87427, got: 86389
There have been errors!