[meta-intel] Issue with ovmf license under Pyro

[Paul Eggleton]

I've heard occasional reports of this issue as well and I believe it has to do 
with the exact sequence of actions up to receiving the error - just setting 
the configuration to be the same won't trigger it. Perhaps you need to add 
something to the image and then remove it, perhaps removing the recipe 
altogether? Not sure.

Cheers,
Paul

On Wednesday, 4 October 2017 4:38:27 AM NZDT Wold, Saul wrote:
> On Mon, 2017-10-02 at 19:41 +0200, Dominig Ar Foll wrote:
> > Hello,
> > 
> > I am seeing an issue with the ovmf license in AGL,  since yocto has
> > moved to Pyro.
> > I can fix by deactivating it, but I do not understand why I see the
> > error.
> > 
> Hi Dominig, 
> 
> I tried to build the AGL code based on the website, I did not see this,
> so clearly your using different branches or code.
> 
> Could you point me at what your actually using please, I want to
> confirm is this is an AGL issue or an OE-Core/meta-intel issue.
> 
> I tried with AGL master and moved meta-intel to master (from pyro), but
> could not reproduce this issue.
> 
> 
> > So it will come back each time that I sync on meta-intel agin.
> > 
> > Any help would be welcome.
> > Log and corrective patches are bellow.
> > 
> That's not really an acceptable patch for this situation.
> 
> Sau!
> 
> > Any help would be welcome.
> > 
> 


-- 

Paul Eggleton
Intel Open Source Technology Centre