From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] getting digest verification failed when emerging bittorrent
Date: Sat, 7 Mar 2009 23:34:59 +0200 [thread overview]
Message-ID: <200903072334.59786.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <18866.58662.461863.309516@ccs.covici.com>
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 <path_to_ebuild_file> manifest
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2009-03-07 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 21:20 [gentoo-user] getting digest verification failed when emerging bittorrent John covici
2009-03-07 21:34 ` Alan McKinnon [this message]
2009-03-07 21:54 ` Dale
2009-03-07 22:35 ` Alan McKinnon
2009-03-08 5:06 ` John covici
2009-03-08 18:29 ` Alan McKinnon
2009-03-08 9:25 ` Neil Bothwick
2009-03-08 9:56 ` Mike Kazantsev
2009-03-08 10:52 ` AllenJB
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200903072334.59786.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox