From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id E727CE00B44; Thu, 5 Nov 2015 05:16:36 -0800 (PST) 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 4C43CE00B3D for ; Thu, 5 Nov 2015 05:16:32 -0800 (PST) Received: by mail.chez-thomas.org (Postfix, from userid 1998) id 435CEF811DC; Thu, 5 Nov 2015 06:16:32 -0700 (MST) Received: from [192.168.1.114] (zeus [192.168.1.114]) by mail.chez-thomas.org (Postfix) with ESMTP id D6BC9F811D7; Thu, 5 Nov 2015 06:16:31 -0700 (MST) To: Yocto Project From: Gary Thomas Message-ID: <563B5700.3050306@mlbassoc.com> Date: Thu, 5 Nov 2015 06:17:52 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Subject: tarballs from git 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: Thu, 05 Nov 2015 13:16:37 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit I use BB_GENERATE_MIRROR_TARBALLS = "1" to generate tarballs from the various git-based recipes I use. For the most part this works great and once the tar file is generated, it just gets reused. However, just now I rebuilt my kernel which uses such a git SRC_URI and the tar file was rebuilt even though I can't see anything that was newly fetched. I had built from the same recipe yesterday (today I only touched a patch which changed neither the recipe nor the SRCREV, etc) and the tar file from last month was used. Looking through the generated tar file, I can see that the last file updated was last Oct 5, so there should have been no reason to rebuild the tar file. Is there some trace (log file, etc) that might tell me why this happened? -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------