[OE-core] Shortened git hashes causing pain

[Gary Thomas]

On 2013-05-23 16:52, Richard Purdie wrote:
> On Thu, 2013-05-23 at 09:28 -0600, Gary Thomas wrote:
>> The shortening of the git hashes in this commit
>>     commit 77fc40a0f843e2488b356d90b64ef436c11c9973
>>     Author: Richard Purdie <richard.purdie at linuxfoundation.org>
>>     Date:   Sun May 19 13:21:55 2013 +0300
>>       bitbake: fetch2: Shorten long srcrevs
>> is causing some problems.
>>
>> I have a simple .bbappend for gtk-sato-engine (attached) which
>> just applies a one-line patch.  When I build this recipe, I
>> get two different work trees (this is from scratch):
>> $ ls -l tmp/work/cobra4430p82-amltd-linux-gnueabi/gtk-sato-engine
>> total 8
>> drwxrwxr-x  3 gthomas gthomas 4096 May 23 09:12 0.3.3+gitAUTOINC+4740ad8d53aba4368ce3e03b06cfdc69eb86dcdc-r0
>> drwxrwxr-x 11 gthomas gthomas 4096 May 23 09:13 0.3.3+gitAUTOINC+4740ad8d53-r0
>>
>> Note: it doesn't seem to happen for the virgin gtk-sato-engine
>> recipe, only when my patch is applied.
>
> Try moving the cache directory in tmp/ out the way. I suspect some kind
> of caching issue since there should not be two work directories. What is
> the contents of each?

Wow, that caused a boatload of other packages to be rebuilt, including
qemu-native, which took forever :-(

This did remove the problem - there is now only the build tree with
the short hash name.  Sadly, it's also now forcing me to basically
rebuild everything to get back to being able to build my image, just
what I didn't want to happen.

Oh well, once this finished I'm sure all will be fine again.  At least
my pain may help others that might experience this, although I don't
know how many folks do very long term development/builds in a single
tree.  This one has been one of my main projects and was started in
early March with more than 500 builds (entries in tmp/log/cooker)!

Thanks

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