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.
>
>
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 no
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.
>
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 th
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 n
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
bu
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 t
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
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
b
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 i
Is there a good way to get file permission changes into ones source package
automaticly ?
This is my scenario: I have rebuilt the build system for the package ketm to
automake/autoconf. This has generated a new configure file. So far so good.
Problem is that the diff from the original source d
Is there a good way to get file permission changes into ones source package
automaticly ?
This is my scenario: I have rebuilt the build system for the package ketm to
automake/autoconf. This has generated a new configure file. So far so good.
Problem is that the diff from the original source
12 matches
Mail list logo
