Comment 20 for bug 38227

yes, kdissert needs new upload with fresh orig version to overlap the differences between the archive and the DB properly, as you did for digikam.

After some investigation with kiko we figured out that what was in archive as Kdissert_1.0.5.debian.orig.tar.gz, didn't fit with what the systems recognizes as such.

What exactly happened is a new upload was accepted with a new orig content but the same name, but at the end, the publisher refused to overwrite the file in archive. (boom, inconsistency between archive and model, but not even a single warn).

The DB has, let's say for comparison sake, kdissert_1.0.5.debian2.orig.tar.gz contents but named as the former.

We expect a new full upload would fix the archive snapshot, but the history will be broken.