Package: dgit Version: 2.14 As part of the response to #849041 I have tried rewinding the history of an affected repository. I have discovered that dgit fetch does a wrong thing: it stitches the bad history back into the remote tracking branch.
This is because it can't tell the difference between "history was rewritten" and "this .dsc was moved in the archive". To make this right, dgit needs more information. I intend to have the dgit git server provide a table of rewritten or banned commits, which can be used to help interpret the Dgit: field in a .dsc. Ian. -- Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.