On Sat, Mar 29, 2008 at 9:23 AM, Mark Knecht <[EMAIL PROTECTED]> wrote:
> On Sat, Mar 29, 2008 at 9:10 AM, Kevin O'Gorman <[EMAIL PROTECTED]> > wrote: > > I cannot emerge world any more because portage keeps barfing on some > random > > java ebuild. > > Java's not even in the list of things to emerge, but here's what I see: > > > > Total: 14 packages (14 upgrades), Size of downloads: 99,898 kB > > > > Would you like to merge these packages? [Yes/No] yes > > >>> Verifying ebuild Manifests... > > > > !!! Digest verification failed: > > !!! /usr/portage/dev-java/sun-jdk/sun-jdk-1.5.0.15-r1.ebuild > > !!! Reason: Failed on RMD160 verification > > !!! Got: 751637964edd458f00c9c72de8f5375eabaf9004 > > !!! Expected: c7268656bf1adccafde5dd9c1104c5a12905b1dc > > treat init.d # > > > > > > I've tried deleting the offending file and re-syncing, but the same > error > > occurs. > > > > Help??? > > > > ++ kevin > > > > -- > > Kevin O'Gorman, PhD > > > > For now mask java above whatever revision is currently installed and > move on. When your emerge is complete remember to remove the mask. > When they fix the file/digest/whatever is causing the problem it will > start working again. > Unfortunately, that puts portage into a proper tizzy because my current version is not longer listed as available (sun-jdk-1.6.0.03). Portage therefore goes into a fit of downgrades, which I do not want. I find that I can get stuff emerged by doing --pretend, then emerging everything except java. This, of course, is not the Way It Should Be (TM), but may get me through the rough patch. ++ kevin -- Kevin O'Gorman, PhD
