From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.chez-thomas.org (mail.mlbassoc.com [65.100.170.105]) by mail.openembedded.org (Postfix) with ESMTP id BDFAC6A378 for ; Thu, 23 May 2013 23:04:07 +0000 (UTC) Received: by mail.chez-thomas.org (Postfix, from userid 1998) id F3172F811F2; Thu, 23 May 2013 17:04:08 -0600 (MDT) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hermes.chez-thomas.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED,BAYES_00 autolearn=unavailable version=3.3.2 Received: from [192.168.1.114] (zeus [192.168.1.114]) by mail.chez-thomas.org (Postfix) with ESMTP id EBDB0F811F2; Thu, 23 May 2013 17:04:05 -0600 (MDT) Message-ID: <519EA06B.4060604@mlbassoc.com> Date: Thu, 23 May 2013 17:04:11 -0600 From: Gary Thomas User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: Patches and discussions about the oe-core layer References: <519E359B.2010203@mlbassoc.com> In-Reply-To: <519E359B.2010203@mlbassoc.com> Subject: Re: Shortened git hashes causing pain X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 23:04:07 -0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 2013-05-23 09:28, Gary Thomas wrote: > The shortening of the git hashes in this commit > commit 77fc40a0f843e2488b356d90b64ef436c11c9973 > Author: Richard Purdie > 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. > > I discovered this when I tried building in an existing tree which > had been built before the mentioned change to the fetch code. There > were sstate files that used the long hash that the build seemed to > want to use but got terribly confused and ended up creating empty > packages, breaking my build. Trying to run 'cleansstate' on the > failing packages did nothing as the code only cleans up based on > the new hash and left the old files still there... > BTW, this caused such a mess in my build tree that I nearly had to start completely from scratch. I was able to recover only by very drastic measures - the following steps were used on more than a dozen packages that got confused: find sstate-cache -name "*${PKG}*" -exec rm -fr \{} \; rm -fr tmp/stamps/*/${PKG} bitbake ${PKG} -c cleansstate rm -fr tmp/work/*/${PKG} Anything less that this giant sledge-hammer and the confusion only continued. At least now I can build my images again... -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------