[yocto] fetch task not run after SRCREV updated

ezekiel at sanborndeasis.net ezekiel at sanborndeasis.net
Wed Oct 1 15:00:34 PDT 2014


Is this the fix

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=202ae5af74f546a9788290a96b0f3c370ee047b2

-Ezekiel

Message: 1
Date: Tue, 30 Sep 2014 17:26:27 -0600
From: Gary Thomas <gary at mlbassoc.com>
To: yocto at yoctoproject.org
Subject: Re: [yocto] fetch task not run after SRCREV updated
Message-ID: <542B3C23.1040509 at mlbassoc.com>
Content-Type: text/plain; charset=windows-1252; format=flowed

On 2014-09-30 17:00, ezekiel at sanborndeasis.net wrote:
> I noticed that if I update the SRCREV value in a recipe to a newer rev for a GIT repository, OE does not think it needs to run the fetch step unless I force it. In other words
>
> bitbake -c fetch foobar
>
> does not pick up that the SRCREV it was downloaded for is no longer correct.
>
> bitbake -f -c fetch foobar
>
> obviously works fine. It appears to come down to the do_fetch stampfile. Is this intended functionality? It seems that if my SRCREV does not match against what was downloaded that
> should be invalidated and the fetch should be forced. Am I missing something?

Check the recent [last week or so] logs - this has just been addressed
and should work with the latest master [or maybe master-next]

-- 
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------



More information about the yocto mailing list