From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LgFGK-0005YU-83 for garchives@archives.gentoo.org; Sun, 08 Mar 2009 09:25:36 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 27CEDE0659; Sun, 8 Mar 2009 09:25:35 +0000 (UTC) Received: from mail.digimed.co.uk (82-69-83-178.dsl.in-addr.zen.co.uk [82.69.83.178]) by pigeon.gentoo.org (Postfix) with ESMTP id 8911EE0659 for ; Sun, 8 Mar 2009 09:25:34 +0000 (UTC) Received: from krikkit.digimed.co.uk (krikkit.digimed.co.uk [192.168.1.3]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.digimed.co.uk (Postfix) with ESMTPSA id 782FC31E705 for ; Sun, 8 Mar 2009 09:25:32 +0000 (GMT) Date: Sun, 8 Mar 2009 09:25:19 +0000 From: Neil Bothwick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] getting digest verification failed when emerging bittorrent Message-ID: <20090308092519.433c39f8@krikkit.digimed.co.uk> In-Reply-To: <49B2ED0E.9060605@gmail.com> References: <18866.58662.461863.309516@ccs.covici.com> <200903072334.59786.alan.mckinnon@gmail.com> <49B2ED0E.9060605@gmail.com> Organization: Digital Media Production X-Mailer: Claws Mail 3.7.1cvs2 (GTK+ 2.14.7; i686-pc-linux-gnu) X-GPG-Fingerprint: 7260 0F33 97EC 2F1E 7667 FE37 BA6E 1A97 4375 1903 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: multipart/signed; boundary="Sig_/rV36zWaSEscAFEtKxvRBQ4B"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Archives-Salt: b13a09ea-adfc-448f-a89b-7228fd43596a X-Archives-Hash: e60ae0b26c8b14b7d37927170d50f799 --Sig_/rV36zWaSEscAFEtKxvRBQ4B Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 07 Mar 2009 15:54:22 -0600, Dale wrote: > > wait 24 hours, resync, try again. > > > > Or just re-digest the package manually: > > > > ebuild manifest Bear in mind this overrides the security that digests provide, although it is harmless when it is only a Chnagleog file. > Does emerge --digest still exist? I recall using something like that a > long time ago. I think I used it for googleforearth which never > matches. That's not a good idea as the mismatch could be caused by a hacked source or binary file. The problem with Google Earth was that they used unversioned tarballs. Whenever you gt a digest error on a distfile, the first step is to delete the distfile and let emerge download it again. If that doesn't help, resync and then check Bugzilla. Don't redigest a distfile unless you can e 100% certain of its validity. --=20 Neil Bothwick Klingons do NOT sweat! They perspire with honour! --Sig_/rV36zWaSEscAFEtKxvRBQ4B Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (GNU/Linux) iEUEARECAAYFAkmzjwUACgkQum4al0N1GQOQ0ACWKmgWRDUl5hWeRfRKaHcF0lSa UgCgxh5SKVaRL63J7LWl3x/7b6pqbkE= =s4Z2 -----END PGP SIGNATURE----- --Sig_/rV36zWaSEscAFEtKxvRBQ4B--