[yocto] Strange sstate problem

[Paul Eggleton]

On Sunday 14 June 2015 14:31:34 Gary Thomas wrote:
> On 2015-06-10 13:58, Gary Thomas wrote:
> > I'm building for two similar targets and sharing sstate between
> > them.  Actually, I build for target A and use that sstate cache
> > in my SSTATE_MIRRORS for target B.
> > 
> > If I try to build target B from scratch, i.e. wipe out most
> > 
> > everything from my build tree:
> >    % mv cache sstate-cache tmp old2; rm -fr old&
> > 
> > I also have a PR server for each target - in local.conf:
> >    PRSERV_HOST = "localhost:0"
> > 
> > When I build in target B, I'm getting a ton of QA errors, basically
> > one for every package selected, e.g.
> > 
> >    ERROR: QA Issue: Package version for package fsl-alsa-plugins went
> >    backwards which would break package feeds from (0:1.0.25-r0.2 to
> >    0:1.0.25-r0.0) [version-going-backwards]> 
> > What could be going on here?
> > 
> > n.b. I'm using a fairly recent Poky/Yocto master
> > (a05663bfa10352fd5af6ca9a9d7b323c1c099f35)
>
> I discovered what was causing these errors - I have buildhistory
> enabled for target B.  Periodically I rebuild target A from scratch
> and this gives buildhistory on target B fits.  For now, I'll just
> disable buildhistory...
> 
> BTW, except for the buildhistory "errors", using sstate like
> this does help quite a lot.

FWIW buildhistory is only trying to help preserve the ability to do upgrades 
from your feeds here - if you don't care to see such errors you can remove 
"version-going-backwards" from your ERROR_QA value.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre