From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by mail.openembedded.org (Postfix) with ESMTP id 66C37780EC for ; Fri, 23 Jun 2017 14:57:50 +0000 (UTC) Received: from hex ([192.168.3.34]) (authenticated bits=0) by dan.rpsys.net (8.15.2/8.15.2/Debian-3) with ESMTPSA id v5NEvnQ5018519 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Fri, 23 Jun 2017 15:57:51 +0100 Message-ID: <1498229869.24449.133.camel@linuxfoundation.org> From: Richard Purdie To: Matthew McClintock , akuster808 Date: Fri, 23 Jun 2017 15:57:49 +0100 In-Reply-To: References: <1496408567-18673-1-git-send-email-richard.purdie@linuxfoundation.org> <7c5e6653-c5a4-6622-b40f-58f80a238c07@gmail.com> X-Mailer: Evolution 3.18.5.2-0ubuntu3.2 Mime-Version: 1.0 X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.11 (dan.rpsys.net [192.168.3.1]); Fri, 23 Jun 2017 15:57:51 +0100 (BST) X-Virus-Scanned: clamav-milter 0.99.2 at dan X-Virus-Status: Clean Cc: "bitbake-devel@lists.openembedded.org" Subject: Re: [PATCH] siggen: Make calc_taskhash match get_taskhash for file checksums X-BeenThere: bitbake-devel@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussion that advance bitbake development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2017 14:57:51 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Fri, 2017-06-23 at 09:29 -0500, Matthew McClintock wrote: > On Thu, Jun 22, 2017 at 5:29 PM, akuster808 > wrote: > > On 06/22/2017 02:10 PM, Matthew McClintock wrote: > > > > > > > > > Seeing this issue on some older (err, really olderrrr) versions > > > of > > > bitbake. How far back could we backport? > > Technically 1.34, 1.32 and 1.30 (krogoth). How far back is > > "olderrrr' ? > I guess I'm seeing this on krogoth so that would be good. Did backporting the patch fix it? There are a variety of ways you could hit this error and I want to confirm it was this specific issue you were hitting... Cheers, Richard