On Tue, 27 May 2014 01:39:11 +0200 Guillem Jover <guil...@debian.org> wrote: > Sorry, the logic there was wrong. I'll change the code to try each > patch, if the first one applies, then apply them all, otherwise try > each other and as long as none applies, ignore that as assuming they > are already applied, but if a single patch applies when the previous > ones all failed, then abort because there's something fishy. Which > should also have no performance impact on the normal case, as > unpacking should succeed when applying the first patch.
Did you apply this change to dpkg-source ? I have a case [1] where a change to upstream source is not detected. The change was done by applying a patch from debian/patches. Once this change is archived, dpkg-source does not detect the change and does not apply the patch. I don't mind this behavior, but dpkg-source should emit a message that mention a skipped patch. All the best [1] Seen with moarvm package: git+ssh://git.debian.org/git/pkg-rakudo/pkg-moarvm.git commit e6ad5d0853886ae73e1348d9ca6ced8e207f9a45 -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
