Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: db compile failure
Date: Wed, 08 Jan 2014 15:22:35 +0000	[thread overview]
Message-ID: <1389194555.6899.105.camel@ted> (raw)
In-Reply-To: <CAJTo0LYZ8DG9V+C3_C=uXt+yV2i2OfnSZwQGEhnAHQ7gPsAN=g@mail.gmail.com>

On Wed, 2014-01-08 at 14:21 +0000, Burton, Ross wrote:
> Hi Jack,
> 
> There were some sstate/manifest changes to master before Christmas
> which is why this happens.  You should only get the warning once per
> package as it rebuilds and updates the manifest, or just delete tmp:
> it will be rebuilt from sstate quickly.

The manifest file names changed and cause those spurious warnings. A
clean tmp dir or wiping out the stale (or all) manifest files in
tmp/sstate-control will "fix" that.

Cheers,

Richard





      reply	other threads:[~2014-01-08 15:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 14:16 db compile failure Jack Mitchell
2014-01-08 14:18 ` Jack Mitchell
2014-01-10 12:43   ` Paul Barker
2014-01-08 14:21 ` Burton, Ross
2014-01-08 15:22   ` Richard Purdie [this message]

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=1389194555.6899.105.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox