From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] ark-4.4.5-cli7zip.patch - Digest verification failed
Date: Fri, 17 Sep 2010 18:23:30 -0700 [thread overview]
Message-ID: <AANLkTinXCk=yWJ+YLKk0UBXMyiJJmPXHwU0e4e-mQMxL@mail.gmail.com> (raw)
Hi,
I've been looking at this failure for maybe a week now thinking one
of these days it would get cleaned up on the servers. Is anyone else
seeing it?
firefly ~ # emerge -DuN @world
Calculating dependencies... done!
>>> Verifying ebuild manifests
!!! Digest verification failed:
!!! /usr/portage/kde-base/ark/files/ark-4.4.5-cli7zip.patch
!!! Reason: Failed on RMD160 verification
!!! Got: 285b725e7542b78815f0f909a65b4b6ec20cee89
!!! Expected: 57369a955bff3038ad0c105eea0179bbb795a030
firefly ~ #
Google isn't turning anything up. Normally these things get cleared
up within about a day but this time around I'm starting to wonder if I
have some other problem here and this is only a symptom?
I'm sure there's some way I can get past it WRT emerge but I'd
rather get it handled at the source if possible. I though about
deleting things in the path shown above but I haven't ever removed
anything except distfiles and didn't want to start now.
I can copy files from other systems if that's a good way around the issue.
Thanks,
Mark
next reply other threads:[~2010-09-18 2:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 1:23 Mark Knecht [this message]
2010-09-18 8:13 ` [gentoo-user] ark-4.4.5-cli7zip.patch - Digest verification failed Albert Hopkins
2010-09-19 17:02 ` Mark Knecht
2010-09-19 18:13 ` Alan McKinnon
2010-09-19 18:45 ` Mark Knecht
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='AANLkTinXCk=yWJ+YLKk0UBXMyiJJmPXHwU0e4e-mQMxL@mail.gmail.com' \
--to=markknecht@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