public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mark Knecht" <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge -aDNvu world fails
Date: Sat, 29 Mar 2008 10:27:53 -0700	[thread overview]
Message-ID: <5bdc1c8b0803291027g18e9bc7v1eb8b278c0532e23@mail.gmail.com> (raw)
In-Reply-To: <9acccfe50803290941w56829d8cj9b0353c268629fe2@mail.gmail.com>

On Sat, Mar 29, 2008 at 9:41 AM, Kevin O'Gorman <kogorman@gmail.com> wrote:
>
> On Sat, Mar 29, 2008 at 9:23 AM, Mark Knecht <markknecht@gmail.com> wrote:
>
>
> >
> >
> >
> > On Sat, Mar 29, 2008 at 9:10 AM, Kevin O'Gorman <kogorman@gmail.com>
> 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
>
Yeah, that's a drag. Not the way it's supposed to work but clearly it
happens once in awhile.

Typically I don't do emerge -DuN world anymore but rather run emerge
-pvDuN world, pick an app that has some dependencies, emerge that app
to pick up stuff and work my way through the list until I'm down to
just a few. I never emerge everything I see in the list since most are
dependencies themselves and I don't want to add them to my world file.

Good luck,
Mark
-- 
gentoo-user@lists.gentoo.org mailing list



  reply	other threads:[~2008-03-29 17:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-29 16:10 [gentoo-user] emerge -aDNvu world fails Kevin O'Gorman
2008-03-29 16:23 ` Mark Knecht
2008-03-29 16:41   ` Kevin O'Gorman
2008-03-29 17:27     ` Mark Knecht [this message]
2008-03-29 17:46       ` Norberto Bensa
2008-03-29 17:56         ` Mark Knecht
2008-03-29 18:31           ` Mike Edenfield
2008-03-29 19:22           ` Neil Bothwick
  -- strict thread matches above, loose matches on Subject: below --
2008-03-30  5:22 Gregory Shearman
2008-03-31 16:31 ` Kevin O'Gorman
2008-04-01 12:07 Gregory Shearman

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=5bdc1c8b0803291027g18e9bc7v1eb8b278c0532e23@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