Hi, On Tue, 03 Jul 2012, David Bremner wrote: > 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.
Just to confirm that we speak of the same thing... you have all patches applied but you don't have the corresponding quilt metadata in ".pc". When you build the source package, dpkg-source tries to apply all the patches because it detected that the first patch could be applied but it fails on the second patch because it's already applied. Is that right? I'm also not sure that there's any nicer solution... this "feature" has been there to ease the transition between 1.0 and 3.0 (quilt) mainly. I was not expecting that people would continue to create new packages where patches would be pre-applied without the corresponding quilt metadata. What's your use case? Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
