Package: git-buildpackage Version: 0.8.7 The source package (from Debian) llvm-toolchain-3.5_3.5-10.dsc produces different results when extracted by dpkg-source, to when processed using gbp pq import. gbp must apply the patches differently somehow.
(This came to light because it exposed a dgit failure, #848843.) To reproduce: cd Download dget -d dget -d 'http://snapshot.debian.org/archive/debian/20150227T221819Z/pool/main/l/llvm-toolchain-3.5/llvm-toolchain-3.5_3.5-10.dsc' cd .. dpkg-source -x Download/llvm-toolchain-3.5_3.5-10.dsc cd llvm-toolchain-3.5-3.5/ git init rm -rf .pc git add -Af . git commit -q -m 'dpkg-source -x' cd .. dpkg-source --skip-patches -x Download/llvm-toolchain-3.5_3.5-10.dsc w cd w git init git add -Af . git commit -q -m 'dpkg-source --skip-patches -x' gbp pq import git fetch ../llvm-toolchain-3.5-3.5 master:dpkgsource git-diff dpkgsource Observe that the output is not empty. I see a diff to `configure'. FTR, this is not a problem for dgit (well, I think it is not now that I have fixed #848843). dgit will fall back to using dpkg-source's patch application, if gbp fails (via a horror involving a stunt `git apply', as previously discussed). But I thought you would like to know. 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.
