Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 40011 - mdadm digests incorrect?
Summary: mdadm digests incorrect?
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-31 13:07 UTC by Stuart Herbert (RETIRED)
Modified: 2004-02-08 14:21 UTC (History)
0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stuart Herbert (RETIRED) gentoo-dev 2004-01-31 13:07:09 UTC 
Attempted to emerge mdadm-1.2.0 and 1.5.0.  On both, emerge reported digest problems.  This is against the CVS tree.

I fixed this by rebuilding the digests.  I have *not* committed the new digests to CVS, in case the fault is local, or in case the mdadm files have been tampered with.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 1 SpanKY gentoo-dev 2004-02-08 12:12:18 UTC 
digests look fine over here ... still a prob for you stuart ?
Comment 2 Stuart Herbert (RETIRED) gentoo-dev 2004-02-08 14:15:36 UTC 
Yeah.  The digest on the mdadm-1.5.-tgz file is fine.  It's complaining that the Manifest has the wrong MD5 for mdadm-1.0.1.ebuild.

The Manifest has this:
MD5 8afb0e20ecdb7142c5296adb33d5504f mdadm-1.0.1.ebuild 1041

but Portage (and md5sum from the command-line) shows this:
521b22a836be669e8f67567f56106d19  mdadm-1.0.1.ebuild

I've refreshed the files from CVS, and get the same results.

Stu
Comment 3 SpanKY gentoo-dev 2004-02-08 14:21:49 UTC 
nah, just seems woods didnt regenerate the Manifest when adding alpha to 1.0.1