Re: fixing permissions
On Fri, Jan 04, 2002 at 10:07:52PM +0100, Magnus Ekdahl wrote: I could fix the problem by manually by adding a chmod +x ./configure somewhere in the rules section. But manually adding a diff seems somewhat clumsy. The chmod seems fine to me. The same problem exists with debian/rules ie it will be not be executable after the patch is applied. It has to be changed by the build process (debuild does it and the autobuilders must too; dpkg-buildpackage bombs out instead). Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fixing permissions
On Fri, Jan 04, 2002 at 10:07:52PM +0100, Magnus Ekdahl wrote: I could fix the problem by manually by adding a chmod +x ./configure somewhere in the rules section. But manually adding a diff seems somewhat clumsy. Other ways to do it include changing the tarball or running autoconf at build time (though that has some rather nasty gotchas). -- You grabbed my hand and we fell into it, like a daydream - or a fever. msg05137/pgp0.pgp Description: PGP signature
Re: fixing permissions
Hi Magnus! You wrote: extracting original source code patching original code using ketm_0.0.6-1.diff.gz trying to run ./configure /bin/sh: ./configure: /bin/sh: bad interpreter: Permission denied I could fix the problem by manually by adding a chmod +x ./configure somewhere in the rules section. But manually adding a diff seems somewhat clumsy. The easiest way is probably just running sh ./configure from debian/rules instead of just ./configure. -- Kind regards, +---+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fixing permissions
On Fri, Jan 04, 2002 at 10:07:52PM +0100, Magnus Ekdahl wrote: Is there a good way to get file permission changes into ones source package automaticly ? Diffs cannot preserve permissions. The only way you can achieve this is either to generate a fresh tarball (probably a bad idea if you're not the upstream maintainer) or, as you mentioned, to run chmod before running the script. -- Colin Watson [[EMAIL PROTECTED]] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fixing permissions
On Sun, Jan 06, 2002 at 02:11:37PM +1100, Hamish Moffatt wrote: On Fri, Jan 04, 2002 at 10:07:52PM +0100, Magnus Ekdahl wrote: I could fix the problem by manually by adding a chmod +x ./configure somewhere in the rules section. But manually adding a diff seems somewhat clumsy. The chmod seems fine to me. The same problem exists with debian/rules ie it will be not be executable after the patch is applied. It has to be changed by the build process (debuild does it and the autobuilders must too; dpkg-buildpackage bombs out instead). dpkg-source makes debian/rules executable, so this isn't a problem when building from freshly downloaded source. -- Colin Watson [[EMAIL PROTECTED]] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: fixing permissions
On Fri, Jan 04, 2002 at 10:07:52PM +0100, Magnus Ekdahl wrote: I could fix the problem by manually by adding a chmod +x ./configure somewhere in the rules section. But manually adding a diff seems somewhat clumsy. The chmod seems fine to me. The same problem exists with debian/rules ie it will be not be executable after the patch is applied. It has to be changed by the build process (debuild does it and the autobuilders must too; dpkg-buildpackage bombs out instead). Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: fixing permissions
Hi Magnus! You wrote: extracting original source code patching original code using ketm_0.0.6-1.diff.gz trying to run ./configure /bin/sh: ./configure: /bin/sh: bad interpreter: Permission denied I could fix the problem by manually by adding a chmod +x ./configure somewhere in the rules section. But manually adding a diff seems somewhat clumsy. The easiest way is probably just running sh ./configure from debian/rules instead of just ./configure. -- Kind regards, +---+ | Bas Zoetekouw | Si l'on sait exactement ce | || que l'on va faire, a quoi| | [EMAIL PROTECTED] | bon le faire?| |[EMAIL PROTECTED] | Pablo Picasso | +---+
Re: fixing permissions
On Fri, Jan 04, 2002 at 10:07:52PM +0100, Magnus Ekdahl wrote: Is there a good way to get file permission changes into ones source package automaticly ? Diffs cannot preserve permissions. The only way you can achieve this is either to generate a fresh tarball (probably a bad idea if you're not the upstream maintainer) or, as you mentioned, to run chmod before running the script. -- Colin Watson [EMAIL PROTECTED]
Re: fixing permissions
On Sun, Jan 06, 2002 at 02:11:37PM +1100, Hamish Moffatt wrote: On Fri, Jan 04, 2002 at 10:07:52PM +0100, Magnus Ekdahl wrote: I could fix the problem by manually by adding a chmod +x ./configure somewhere in the rules section. But manually adding a diff seems somewhat clumsy. The chmod seems fine to me. The same problem exists with debian/rules ie it will be not be executable after the patch is applied. It has to be changed by the build process (debuild does it and the autobuilders must too; dpkg-buildpackage bombs out instead). dpkg-source makes debian/rules executable, so this isn't a problem when building from freshly downloaded source. -- Colin Watson [EMAIL PROTECTED]
