patch 2.6 rejects relative paths

patch 2.6 rejects relative paths

[Elena Vengerova]

Hello,

I have patch 2.6.1 on my Fedora.
I've found out that it rejects patches like 
recipes/tcltk/tcl-8.5.8/mips-tclstrtod.patch with relative paths:

--- ../generic/tclStrToD.c.orig
+++ ../generic/tclStrToD.c

I failed to find the reason, but my colleague said me (she was unsure) 
that it was security hole fix.
Thus looks like it's no way to force patch behave like old one.

I wonder if some work around is possible (except patch downgrade) or 
it's necessary to fix the recipes.

Thanks,
     Helen

Re: patch 2.6 rejects relative paths

[Tom Rini]

On 03/29/2011 04:31 AM, Elena Vengerova wrote:
> Hello,
> 
> I have patch 2.6.1 on my Fedora.
> I've found out that it rejects patches like
> recipes/tcltk/tcl-8.5.8/mips-tclstrtod.patch with relative paths:
> 
> --- ../generic/tclStrToD.c.orig
> +++ ../generic/tclStrToD.c
> 
> I failed to find the reason, but my colleague said me (she was unsure)
> that it was security hole fix.
> Thus looks like it's no way to force patch behave like old one.
> 
> I wonder if some work around is possible (except patch downgrade) or
> it's necessary to fix the recipes.

What metadata are you using (and branch name)?  This should be fixed in
current openembedded.org master.

-- 
Tom Rini
Mentor Graphics Corporation

Re: patch 2.6 rejects relative paths

[Elena Vengerova]

On 29.03.2011 18:35, Tom Rini wrote:
> On 03/29/2011 04:31 AM, Elena Vengerova wrote:
>> Hello,
>>
>> I have patch 2.6.1 on my Fedora.
>> I've found out that it rejects patches like
>> recipes/tcltk/tcl-8.5.8/mips-tclstrtod.patch with relative paths:
>>
>> --- ../generic/tclStrToD.c.orig
>> +++ ../generic/tclStrToD.c
>>
>> I failed to find the reason, but my colleague said me (she was unsure)
>> that it was security hole fix.
>> Thus looks like it's no way to force patch behave like old one.
>>
>> I wonder if some work around is possible (except patch downgrade) or
>> it's necessary to fix the recipes.
> What metadata are you using (and branch name)?  This should be fixed in
> current openembedded.org master.
>
I use release-2011.03 (I hope).
Sorry, I'm new in OE, not sure what do you exactly mean by "metadata" 
(the term itself is bit ambiguous).
I'm trying to build meta-toolchain recipe with local config almost same 
as sample one.

Nice to hear that it's fixed.

Thanks a lot,
     Elena