From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 42D911384B4 for ; Sun, 15 Nov 2015 19:05:49 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 65FE821C116; Sun, 15 Nov 2015 19:05:41 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 5B21B21C111 for ; Sun, 15 Nov 2015 19:05:40 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Zy2cH-0004Ml-01 for gentoo-user@lists.gentoo.org; Sun, 15 Nov 2015 20:05:33 +0100 Received: from pc123.math.cas.cz ([147.231.88.123]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 15 Nov 2015 20:05:32 +0100 Received: from martin by pc123.math.cas.cz with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 15 Nov 2015 20:05:32 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Martin Vaeth Subject: [gentoo-user] Re: All sorts of digest verification failures Date: Sun, 15 Nov 2015 19:05:26 +0000 (UTC) Message-ID: References: <20151112171903.68e1b944@hal9000.localdomain> <5644C238.6040008@gmail.com> <20151115095928.GA1766@acm.fritz.box> <20151115171735.4fd31dc3@digimed.co.uk> X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pc123.math.cas.cz User-Agent: slrn/1.0.1 (Linux) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Archives-Salt: 2c0315a1-967b-4683-a459-00a17e082854 X-Archives-Hash: 6d9f9586384ad22b36dd0fd336dccfd9 Neil Bothwick wrote: > > I deleted the busybox directory from the tree then ran emerge --sync. > The error is still there You have the same files that I have. Unfortunately, only now I actually did: $ grep busybox-9999 Manifest EBUILD busybox-9999.ebuild 8580 [...] ??? I have the same wrong size recorded in the Manifest! No idea why portage didn't yell at me - there seems to be another bug involved. So, sorry, my previous conjecture was wrong. The only information which I can give you currently, is that probably all mirrors contain the same broken Manifest in the moment. *Perhaps* (a very wild conjecture!) the reason why this Manifest got not updated is the same bug which caused portage not to yell at me, despite the broken Manifest. As a temporary hack, calling "ebuild manifest" on that file is probably the only reasonable way to proceed, but this problem must be fixed, of course...