Package: dgit Version: 9.6 I have been investigating #1018143 confusion regarding mode changes and patch formats #995056 re files changing mode
I have a wip branch which uses git diff to generate patches, rather than dpkg-source --commit, and in my tests it can generate patches that, when dpkg-source extracts them, manipulate file modes. However, all of this breaks with single-debian-patch. That optionc auses dpkg to try to unapply, and then regenerate, the changes in that patch. This does not work if the patch is not one that dpkg-source can generate. This means that "3.0 (quilt) single-debian-patch" is able to properly represent strictly fewer trees than "3.0 (quilt) vanilla". The failure modes are very bad. For example, I was able to make a source package which extracts correctly, and everything is fine, but as soon as you try to edit *an unrelated file* dpkg-source craps out terribly. I am filing this against dgit because I CBA to try to write a bug report against src:dpkg right now. Writing that report will involve some double-checkng and perhaps some care in the wording. I think in src:dgit we need to implement an alternative to single-debian-patch and recommend that instead. Perhaps it could be a quilt mode, which strips the package back down to the .origs and makes a single patch out of the delta? Ian. -- Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
