How to proceed ? I Found an error in pseudo_native that has been corrected in a latter commit

How to proceed ? I Found an error in pseudo_native that has been corrected in a latter commit

[Lars Larsen]

Hello world

We are using Morty branch of Yocto.
I have been compiling a lot on a 64 bit host (Ubuntu -14-04), for a 32 
bit  x86 target , it is working fine.

Now an other team member should build it, he is using an 32 bit host 
(Ubuntu-12-04)
On his machine for some reason,  I don't know why, bitbake decides that 
it needs to build pseudo_native -  and that build fails.

the errors are very basic syntax errors in some python scripts.
and after investigating the repositories for pseudo_native, I see that 
these errors has been fixed in the pseudo_native repository. But in a 
latter commit than the one Morty pulls in.

How do i proceed ?
I can fix the errors locally and make a .bbappend with a patch that 
correct these specific errors, or change the SRCREV.
I'm unsure about  the correct procedure to follow ?
Can anyone guide me gently ??

thanks in advance

-Lars

-- 

Best Regards
Lars Larsen

F.Poulsen Engineering Aps
Tjørnager 16
4330 Hvalsø
Denmark
+45 29802784
www.visionweeding.com

Re: How to proceed ? I Found an error in pseudo_native that has been corrected in a latter commit

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 473 bytes --]

On 5 January 2017 at 12:05, Lars Larsen <lars@visionweeding.com> wrote:

> I can fix the errors locally and make a .bbappend with a patch that
> correct these specific errors, or change the SRCREV.
> I'm unsure about  the correct procedure to follow ?
>

I'd make a bbappend that changes SRCREV to a newer commit.  If that solves
the problem then depending on how many commits are involved and how
invasive they are you could submit the patch to oe-core.

Ross

[-- Attachment #2: Type: text/html, Size: 889 bytes --]