Calculating dependencies... done! >>> Emerging (1 of 1) dev-db/mysql-5.0.21 to / >>> checking ebuild checksums >>> checking auxfile checksums >>> checking miscfile checksums >>> checking distfiles checksums Traceback (most recent call last): File "/usr/bin/emerge", line 3416, in ? mydepgraph.merge(pkglist) File "/usr/bin/emerge", line 2029, in merge retval=portage.doebuild(y,"merge",myroot,self.pkgsettings,edebug,tree="porttree") File "/usr/lib/portage/pym/portage.py", line 2807, in doebuild (mydo not in ["digest","fetch","unpack"] and File "/usr/lib/portage/pym/portage.py", line 2327, in digestcheck mf.checkFileHashes(mf.findFile(f), f) File "/usr/lib/portage/pym/portage_manifest.py", line 483, in checkFileHashes myhashes = self.fhashdict[ftype][fname] KeyError: 'mysql-patchset-5.0.21-r2.tar.bz2'
I also get this error, same portage version, package: mysql-4.1.19 For now I will mask it and switch back to older version, until this gets fixed.
*** Bug 132427 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > I also get this error, same portage version, package: mysql-4.1.19 > For now I will mask it and switch back to older version, until this gets fixed. I have been too rushy, downgrade won't do any good. The problem is that the md5 digest for mysql-patchset-4.1.19-r1.tar.bz2 is not in the digest-mysql-4.1.19 file. To fix this: ebuild /usr/portage/dev-db/mysql/mysql-4.1.19.ebuild digest emerge -u mysql There should be a graceful error message in such occasion, tough.
(In reply to comment #3) > I have been too rushy, downgrade won't do any good. The problem is that the md5 > digest for mysql-patchset-4.1.19-r1.tar.bz2 is not in the digest-mysql-4.1.19 > file. To fix this: Yeah, this bug is NOT about broken mysql digest. See Bug 132401 for that (already fixed, so please emerge --sync in a while). This one is about portage traceback only, downgrading won't solve the original problem. ;)
This has been fixed in svn r3324.
*** Bug 132551 has been marked as a duplicate of this bug. ***
*** Bug 132557 has been marked as a duplicate of this bug. ***
This has been release in 2.1_pre10-r4.