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 DB0521384B4 for ; Sun, 15 Nov 2015 11:16:15 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B264E21C1A5; Sun, 15 Nov 2015 11:15:25 +0000 (UTC) Received: from lyseo.edu.ouka.fi (unknown [82.128.138.2]) by pigeon.gentoo.org (Postfix) with ESMTP id A999B21C197 for ; Sun, 15 Nov 2015 11:15:24 +0000 (UTC) Received: from [100.87.26.89] (85-76-73-165-nat.elisa-mobile.fi [85.76.73.165]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by lyseo.edu.ouka.fi (Postfix) with ESMTPSA id B83FD156FFF for ; Sun, 15 Nov 2015 13:15:18 +0200 (EET) Subject: Re: [gentoo-user] Re: All sorts of digest verification failures References: <20151112171903.68e1b944@hal9000.localdomain> <5644C238.6040008@gmail.com> <20151115095928.GA1766@acm.fritz.box> <2BE25BAB-1326-4F34-856D-DB87C08291BB@iki.fi> <20151115110153.GD1766@acm.fritz.box> From: Matti Nykyri Content-Type: text/plain; charset=us-ascii X-Mailer: iPhone Mail (11D201) In-Reply-To: <20151115110153.GD1766@acm.fritz.box> Message-Id: <7569230E-A00A-4BF0-818A-0913E4134FF5@iki.fi> Date: Sun, 15 Nov 2015 13:15:16 +0200 To: "gentoo-user@lists.gentoo.org" Content-Transfer-Encoding: quoted-printable 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 (1.0) X-Archives-Salt: b320ea24-ee0e-4603-b2c7-9256d11e12e4 X-Archives-Hash: 62818f90d056474605785b273d4f3701 > On Nov 15, 2015, at 13:01, Alan Mackenzie wrote: >=20 >> Well it's not. It just checks all the manifests and complains about >> errors. It doesn't affect the building of 1.23.1-r1. Ok. I must be using some different switch then. > Ah, OK. But it causes emerge to bail out, so never gets round to > building 1.23.1-r1. >=20 >> If I were you I'ld download the latest portage snapshot. That should >> take care of any remaining issues. Is your portage upto date? >=20 > I'd just synched my portage tree immediately before attempting the build. > I'll try again tomorrow, in the hope everything will have been sorted out > by then. Syncing and getting a new snapshot is a bit different. With a snapshot you g= et a new clean start. Download it and unpack. After that check that your portage package is upto date (emerge -av portage)= . --=20 -Matti=