On 29/10/13 16:50, Dmitry Smirnov wrote: > Dear Ximin, > > While I agree with you that it would be nice to have a big fat warning > when `debuild` attempts to build package with no patches applied, I > must mention that sometimes current behaviour is quite useful. When > you're hacking the source tree and finalising your patches it is > convenient that `debuild -b` is not trying to re-apply them. This is > only happening when you're building with "-b" option. Without "-b" > patches will be applied and `debuild` will fail on any error. >
I'm not sure if I follow. `quilt refresh` syncs debian/patches with your source tree, then re-applying the patches simply has no effect since `dpkg-source --before-build` is idempotent, at least for 3.0 (quilt). You can try it and see: - do a `dpkg-source --before-build` - edit one of the files that the top patch affects - `dquilt refresh`, assuming you have the `dquilt` alias set up - `dpkg-source --before-build` several times more gives no error Also, when I'm hacking on the patches themselves, I skip debuild and just call debian/rules directly (along with rolling back the debhelper logs). > Regarding #728097 that you mentioned you should have build your > package in clean environment (e.g. using pbuilder) in first > place. Many other problems will happen if you're not building in clean > chroot before upload. > I realise this and will go and set that up when I get some time, but my problem there wasn't caused by my build environment. -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
signature.asc
Description: OpenPGP digital signature
