Re: debuild/dpkg-buildpackage behaves not as expected
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 16/05/12 09:34, Andrey Rahmatullin a ?crit :
> On Wed, May 16, 2012 at 09:05:21AM +0200, Olе Streicher wrote:
>> I just discovered that debuild does not behave as I would expect
>> from the maintainer's guide [1]:
>>
>> | Cleaning the source and rebuilding the package from your user
>> account | is as simple as: | $ debuild [...] | You can clean the
>> source tree as simply as: | $ debuild clean
>>
>> This gives an error if the "dh_clean" does not work on the
>> unpatched source, since "debuild" reverts all patches, but
>> "debuild clean" does not apply then. I filed a bug report for
>> this [2], including a simple example package, but the maintainer
>> doesn't see a problem here.
> (for the reference) ... because "debuild is just a wrapper around
> dpkg-buildpackage" and the behavior "is documented in
> dpkg-buildpackage(1)".
>
Documented, yes. Rationalized, no. I agree that there's something
fishy with the default behaviour: anytime you have to patch a file
which is later modified during build, you have to build with -tc IIRC.
I agree with Ole that unpatching should never be done before cleaning.
Regards, Thibaut.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+zX6UACgkQ+37NkUuUiPEe5QCfZDjHOHmCeu6GIKXWTPlXOxkS
TIoAn1sgi+4ufCCc9yTsnYvR3nVDI5gi
=ALCr
-----END PGP SIGNATURE-----
Reply to: