From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: Strange sstate problem
Date: Sun, 14 Jun 2015 14:31:34 -0600 [thread overview]
Message-ID: <557DE4A6.3040703@mlbassoc.com> (raw)
In-Reply-To: <557896F3.2040207@mlbassoc.com>
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.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2015-06-14 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 19:58 Strange sstate problem Gary Thomas
2015-06-12 16:19 ` Robert Berger
2015-06-14 20:31 ` Gary Thomas [this message]
2015-06-16 13:55 ` Paul Eggleton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=557DE4A6.3040703@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.