Package: dpkg-dev Version: 1.16.3 Severity: wishlist If the first patch in a 3.0 (quilt) series is reverted by later patches in the series, then the heuristic used by dpkg-source to detect if patches are applied fails. This might sound contrived, but it can arise if e.g. patches are generated from a version control system.
A workaround is to add "no-preparation" to options or local-options; I'm not sure if a nicer solution is possible. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dpkg-dev depends on: ii base-files 6.7 ii binutils 2.22-6 ii bzip2 1.0.6-1 ii libdpkg-perl 1.16.3 ii libfile-fcntllock-perl 0.14-1+b1 ii make 3.81-8.2 ii patch 2.6.1-3 ii xz-utils 5.1.1alpha+20110809-3 Versions of packages dpkg-dev recommends: pn build-essential 11.5 pn fakeroot 1.18.3-1 pn gcc [c-compiler] 4:4.6.2-4 pn gcc-4.4 [c-compiler] 4.4.7-1 pn gcc-4.6 [c-compiler] 4.6.3-1 pn gnupg 1.4.12-4 pn gpgv 1.4.12-4 pn libalgorithm-merge-perl <none> Versions of packages dpkg-dev suggests: ii debian-keyring 2012.02.22 -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
