Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 180298 - KDE 3.5.7 ebuilds fail md5sum verifications
Summary: KDE 3.5.7 ebuilds fail md5sum verifications
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-30 00:16 UTC by Charles Christie
Modified: 2007-05-30 02:30 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Charles Christie 2007-05-30 00:16:19 UTC
Not the files I download, but the actual ebuilds have wrong md5sums. The first one on the list is nsplugins, and pretty much all of the other ones that I tried that weren't out of another overlay had the same issue.

Reproducible: Always

Steps to Reproduce:
1. emerge --sync
2. emerge -uavDN kde-meta

Actual Results:  
>>> Verifying ebuild Manifests...

!!! Digest verification failed:
!!! /usr/portage/kde-base/nsplugins/nsplugins-3.5.7.ebuild
!!! Reason: Failed on MD5 verification
!!! Got: a00cf3a9ed10ef4b2995a370e09f40a5
!!! Expected: 0c16e4def12cff34886c1d8027b307d8


Expected Results:  
I should be using KDE 3.5.7 right now...

Portage is on an xfs partition, and I already checked it for corruption. I synced multiple times during the past few days and nothing has helped. digesting it all myself is not going to happen, because kde-i18n alone took hours to download a crapton of files I'll never use and digest them.
Comment 1 Jorge Manuel B. S. Vicetto (RETIRED) Gentoo Infrastructure gentoo-dev 2007-05-30 02:26:19 UTC
Charles,

kindly review http://bugs.gentoo.org/page.cgi?id=fields.html#bug_severity
Comment 2 Jorge Manuel B. S. Vicetto (RETIRED) Gentoo Infrastructure gentoo-dev 2007-05-30 02:30:38 UTC
I and many others have been able to update to 3.5.7, therefore, this must be a local problem. Try to sync the tree again and if that doesn't work, try using another mirror.