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 1LgNmA-0006DM-SS for garchives@archives.gentoo.org; Sun, 08 Mar 2009 18:31:03 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D5382E076B; Sun, 8 Mar 2009 18:31:01 +0000 (UTC) Received: from ey-out-1920.google.com (ey-out-1920.google.com [74.125.78.144]) by pigeon.gentoo.org (Postfix) with ESMTP id 9800EE076B for ; Sun, 8 Mar 2009 18:31:01 +0000 (UTC) Received: by ey-out-1920.google.com with SMTP id 13so114906eye.10 for ; Sun, 08 Mar 2009 11:31:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=CCQpKCeZg38m88wAtbTzquTY2xXBtBy229krhQPUdPE=; b=vXnUsscNSx1o3PcqpEpCATuOg4Gc8RvpQ//F3UeU4tr2jPgalUR50VNe3YG5lNXHZv zB91FNGo/yJrt7Q5HhaofGYzoxg8XrmbaokkwTN2+l0uP4SbPtvw/YiySsWRGzJIXIXd mI5vnDOQjKRrBovyrLykj5qkVoQ1O1Iy56g00= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :message-id; b=Vv1W1+a+vfbI91fyxR/+fyZ+zF7riTJHtobgLqGUpHXdE/GxvUSpQuBGknb1M53F6T CV6+D2ttawBqPPC6zQL9WRcK3c8QYhKGxRrJRJL9F+Wm6mqQ09gpLfSkQUDtiTsnEhGj wh2/rkeoKMLshGjSGjrLh0mAuS+86h7qS6snI= Received: by 10.216.12.67 with SMTP id 45mr1806227wey.218.1236537060955; Sun, 08 Mar 2009 11:31:00 -0700 (PDT) Received: from nazgul.localnet (196-210-153-49-rrdg-esr-2.dynamic.isadsl.co.za [196.210.153.49]) by mx.google.com with ESMTPS id k7sm6050626nfh.35.2009.03.08.11.30.59 (version=SSLv3 cipher=RC4-MD5); Sun, 08 Mar 2009 11:31:00 -0700 (PDT) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] getting digest verification failed when emerging bittorrent Date: Sun, 8 Mar 2009 20:29:40 +0200 User-Agent: KMail/1.11.1 (Linux/2.6.28-gentoo-r2; KDE/4.2.1; x86_64; ; ) References: <18866.58662.461863.309516@ccs.covici.com> <49B2ED0E.9060605@gmail.com> <18867.21070.366041.5582@ccs.covici.com> In-Reply-To: <18867.21070.366041.5582@ccs.covici.com> 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="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200903082029.41191.alan.mckinnon@gmail.com> X-Archives-Salt: bb187366-6bf6-47f2-9ca9-bdf45a4c7296 X-Archives-Hash: c0affb97a7cb757c196815c85ce09f2e On Sunday 08 March 2009 07:06:22 John covici wrote: > on Saturday 03/07/2009 Dale(rdalek1967@gmail.com) wrote > > > Alan McKinnon wrote: > > > On Saturday 07 March 2009 23:20:38 John covici wrote: > > >> Hi. I am getting digest verification failed when trying to emerge > > >> bittorrent -- it is having trouble with the Changelog file. The > > >> exact message is: > > >> !!! Digest verification failed: > > >> !!! /usr/portage/net-p2p/bittorrent/ChangeLog > > >> !!! Reason: Filesize does not match recorded size > > >> !!! Got: 19308 > > >> !!! Expected: 19466 > > >> > > >> Is there a new ebuild coming? > > > > > > wait 24 hours, resync, try again. > > > > > > Or just re-digest the package manually: > > > > > > ebuild manifest > > > > 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. > > OK, thanks I was hoping something like that would work. As others have already said (but the importance of it got lost in the ensuing retorts), you have to be careful not to redigest stuff arbitrarily. This case was a mere Changelog which doesn't affect the built binaries and hence is safe. Most digest failures are for one of two reasons: 1. Proprietary binaries that don't think it necessary to tell their customers which version they are getting. They must think customer's are psychic, 2. The developer goofed and forgot to upload one or more changed files. The dangerous case that digests are designed to help you with is malicious changes where you get a trojan. This danger is real and you should take it seriously. The fact that I've never actually *seen* it happen doesn't mean anything and isn't even relevant. -- alan dot mckinnon at gmail dot com