All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "Vuille, Martin (Martin)" <vmartin@avaya.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Another sstate rebuild issue, badly need help understanding sstate
Date: Mon, 3 Nov 2014 17:05:28 +0100	[thread overview]
Message-ID: <20141103160528.GB2799@jama> (raw)
In-Reply-To: <30C2D590D16A5C46ADFE652191037798411585F0@AZ-US1EXMB03.global.avaya.com>

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

On Mon, Nov 03, 2014 at 03:09:43PM +0000, Vuille, Martin (Martin) wrote:
> Hi Richard,
> 
> > -----Original Message-----
> > From: Richard Purdie [mailto:richard.purdie@linuxfoundation.org]
> > Sent: November 03, 2014 10:06 AM
> > 
> > On Mon, 2014-11-03 at 12:53 +0000, Vuille, Martin (Martin) wrote:
> > > I have a variable “REV_TOOLS” defined in distro/conf/somename.conf in
> > > a custom distro layer from a git repo.
> > >
> > > This variable is assigned to SRCREV in a number of recipes (SRCREV =
> > > “${REV_TOOLS}”) for packages included in my images and SDKs.
> > 
> > Can you describe how the value of REV_TOOLS is set? Is it just assigned
> > some value or done with some code?
> > 
> 
> REV_TOOLS = "<some git commit hash string>"
> 
> > Does clearing the bitbake cache make things rebuild as expected (mv
> > tmp/cache tmp/cache-old) ?
> > 
> 
> I did a cleansstate on the affected packages and they rebuild as expected.

Do your packages have SRCPV in PV?

SRCREV isn't included in sstate signature without SRCPV in PV or this
patch:

commit a414b17e1d783ad68a2d0f7d5922967449c05797
Author: Ross Burton <ross.burton@intel.com>
Date:   Mon Sep 29 15:40:14 2014 +0100

    base.bbclass: add SRCREV to do_fetch() hash

but even with this patch it doesn't work for recipes with multiple
repositories (you can find an e-mail with more details in oe-core ML).

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2014-11-03 16:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 12:53 Another sstate rebuild issue, badly need help understanding sstate Vuille, Martin (Martin)
2014-11-03 14:12 ` Paul Eggleton
2014-11-03 14:20   ` Vuille, Martin (Martin)
2014-11-03 15:02   ` Vuille, Martin (Martin)
2014-11-03 15:06 ` Richard Purdie
2014-11-03 15:09   ` Vuille, Martin (Martin)
2014-11-03 16:05     ` Martin Jansa [this message]
2014-11-03 16:18       ` Vuille, Martin (Martin)

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=20141103160528.GB2799@jama \
    --to=martin.jansa@gmail.com \
    --cc=vmartin@avaya.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.