Hi, On Tue, 01 Dec 2009, Cristian Greco wrote: > it seems that calling a debian/rules binary-only build target (i.e. with > dpkg-buildpackage -b, -B or -A option) when package is 3.0 (quilt) source > format and there is no quilt logic (patch/unpatch) in debian/rules (which is > what FAQ[0] page suggests as a *should*) will cause some troubles. > > This is because dpkg-buildpackage won't call dpkg-source if a binary-only > build > has been requested, so patches listed in debian/patches/series won't be > applied > and, moreover, this will cause build fails if debian/rules expects patches to > be applied to accomplish some specific operations.
This is why patches are applied at extraction time... Why don't you apply the patches and why do you expect dpkg-buildpackage to fix it for you ? The default state should now be "patches are applied" and if you unapply them, it's up to you to ensure they are applied again when you run the next build. I understand it can be cumbersome when you use a VCS to manage your package. But maybe the VCS helper tools needs to gain some knowledge of the new format to better assist the user. Cheers, -- Raphaël Hertzog -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
