Re: dpkg-buildpackage, dpatch and wrong permissions...
-----BEGIN PGP SIGNED MESSAGE-----
Frank Küster wrote:
> Claudio Moratti <firstname.lastname@example.org> wrote:
>>On Wednesday 22 February 2006 16:27, Matthijs Mohlmann wrote:
>>>Claudio Moratti wrote:
>>>>I'm not able to find how fix this problem...
>>>>Thx a lot ;-)
>>>This is not really a problem. The point is that diff can't see in a diff
>>>file if a file is executable yes or no, before diff didn't shout this
>>>warning. Anyway my build here goes ok and have also some warnings about
>>>"0755 cannot be represented in diff" warnings. But they shouldn't harm
>>thanks for this explanation!
>>the build process ends correctly, of course, but I'm not able to understand
>>why debian/patches files have not the rw-r--r-- perm...
>>during the unpack of sources, probably, only debian/* files are chmod-ed...
>>could be the reason?
> IIRC, dpatch doesn't call "patch -p<foo> -i debian/patches/<patchfile>",
> but instead it executes the file, and if it's just a normal unified
> diff, there's some magic in the header that causes patch to be called
> properly. Therefore dpatch probably requires that patches be executable
> and just sets the permissions as needed.
> Regards, Frank
If I understand the code of dpatch right then the patch will be chmodded
Search for "chmod +x" in /usr/bin/dpatch and see what is happening after
That's also the reason why the patches are executable afterwards.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----