From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 0CA2CE008DC; Mon, 20 Jul 2015 09:08:33 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mail.chez-thomas.org (mail.mlbassoc.com [65.100.170.105]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id CE5B1E008D4 for ; Mon, 20 Jul 2015 09:08:29 -0700 (PDT) Received: by mail.chez-thomas.org (Postfix, from userid 1998) id 2D314F811DC; Mon, 20 Jul 2015 10:08:29 -0600 (MDT) Received: from [192.168.1.114] (zeus [192.168.1.114]) by mail.chez-thomas.org (Postfix) with ESMTP id 7BF0FF811DA; Mon, 20 Jul 2015 10:08:28 -0600 (MDT) Message-ID: <55AD1D0E.1020402@mlbassoc.com> Date: Mon, 20 Jul 2015 10:08:46 -0600 From: Gary Thomas User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: "Burton, Ross" References: <55AD13AC.3010802@mlbassoc.com> In-Reply-To: Cc: Yocto Project Subject: Re: New/unfamiliar messages X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2015 16:08:33 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 2015-07-20 09:39, Burton, Ross wrote: > > On 20 July 2015 at 16:28, Gary Thomas > wrote: > > NOTE: Stamp /home/local/rpi2_2015-03-05/tmp/stamps/i686-linux/dbus-native/1.8.16-r0 is not reachable, removing related manifests > ... many more > > What do these mean and should I be worried about seeing them? > > > That basically means that e.g. the dbus-native in the layers is newer than the version in the sysroot, so it is now removing dbus-native 1.8.16 from the sysroot so it can later > install 1.8.. Now this code has pretty much proven itself we can probably remove those messages. > > Previously it just wrote over the top and hoped for the best, with logic to error out if one native recipe wrote over another recipe's files. This was good for determinism but bad > for moving files between recipes or renaming recipes (which was impossible). Thanks for the explanation. I can see that the code for this is fairly new (early June) and I must have not seen many of these so it grabbed my attention. The build tree in question was last touched in March, so there obviously were many cases of this situation. Related query: I tend to build & rebuild in the same tree (typically only one platform per build tree) over long periods of time (like my RaspberryPi2 tree which I've had around for many months). Over time, there may be a lot of updated builds and I end up with many "duplicated" trees in my tmp/work (I don't use rm_work), e.g. tmp/work/x86_64-linux/libfontenc-native/1_1.1.3-r0 tmp/work/x86_64-linux/libfontenc-native/1_1.1.2-r0 tmp/work/x86_64-linux/glib-2.0-native/1_2.44.1-r0 tmp/work/x86_64-linux/glib-2.0-native/1_2.44.0-r0 Is there a [simple] way to remove just the old/redundant trees? -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------