Received: from [80.91.229.2] (helo=ciao.gmane.org) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1LnATE-00048j-L8 for openembedded-devel@openembedded.org; Fri, 27 Mar 2009 12:43:32 +0100 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LnARU-00033o-Us for openembedded-devel@openembedded.org; Fri, 27 Mar 2009 11:41:45 +0000 Received: from weppsb02.northropgrumman.com ([155.104.37.18]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 27 Mar 2009 11:41:44 +0000 Received: from jeremy.williams by weppsb02.northropgrumman.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 27 Mar 2009 11:41:44 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: openembedded-devel@openembedded.org From: Jeremy Williams Date: Fri, 27 Mar 2009 11:41:34 +0000 (UTC) Message-ID: References: <200903270903.13523.marcin@juszkiewicz.com.pl> Mime-Version: 1.0 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: main.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 155.104.37.18 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 (.NET CLR 3.5.30729)) Sender: news Subject: Re: [PATCH] Busybox 1.13.2 - modprobe.patch checksum update X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2009 11:43:32 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Marcin Juszkiewicz juszkiewicz.com.pl> writes: > > Dnia piątek, 27 marca 2009 o 00:16:05 Jeremy Williams napisał(a): > > Looks like busybox-1.13.2-modprobe.patch was modified, causing a > > checksum failure. Here's the patch: > > That patch was moved to metadata. Please update. > > Regards, Marcin, Sorry, did not notice that this patch was pulled from metadata. This error, however, occured during build of a metadata pull performed just 18 hours ago. Can you rebuild and confirm the checksum? -jeremy