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 61AAD1384B4 for ; Sun, 15 Nov 2015 20:29:59 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D3D8021C121; Sun, 15 Nov 2015 20:29:50 +0000 (UTC) Received: from mail0131.smtp25.com (mail0131.smtp25.com [75.126.84.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B609021C050 for ; Sun, 15 Nov 2015 20:29:49 +0000 (UTC) Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.14.9/8.14.8) with ESMTP id tAFKTlAH001674 for ; Sun, 15 Nov 2015 15:29:47 -0500 From: covici@ccs.covici.com To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: All sorts of digest verification failures In-reply-to: <5648E8C3.5090509@gmail.com> References: <20151112171903.68e1b944@hal9000.localdomain> <5644C238.6040008@gmail.com> <20151115095928.GA1766@acm.fritz.box> <20151115171735.4fd31dc3@digimed.co.uk> <5648E8C3.5090509@gmail.com> Comments: In-reply-to Dale message dated "Sun, 15 Nov 2015 14:19:15 -0600." X-Mailer: MH-E 8.5; nmh 1.6; GNU Emacs 23.4.1 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 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1672.1447619387.1@ccs.covici.com> Date: Sun, 15 Nov 2015 15:29:47 -0500 Message-ID: <1673.1447619387@ccs.covici.com> X-SpamH-OriginatingIP: 70.109.53.110 X-SpamH-Filter: d-out-001.smtp25.com-tAFKTlML007908 X-Archives-Salt: 6d6d9eab-4250-4743-8494-1b5356d7a78a X-Archives-Hash: 2f1e9bf9419605f0d3ecac29b9831049 Dale wrote: > Martin Vaeth wrote: > > 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... > > > > > > > > > Wasn't there a emerge option to ignore the manifest? I seem to recall > there used to be one but it was a LONG time ago. Of course, if someone > has tinkered with something that would be a bad thing to do. I thought I remembered something where the manifest no longer checks the ebuild, just the file in distfiles -- I thought I remembered seeing this somewhere. It was at a time when we got all the manifests all at once. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com