public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Hemmann, Volker Armin" <volker.armin.hemmann@tu-clausthal.de>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Errors when doing an emerge -uD world
Date: Mon, 17 Oct 2005 10:09:55 +0200	[thread overview]
Message-ID: <200510171009.55681.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <43531195.6080802@mn.rr.com>

On Monday 17 October 2005 04:51, John C. Shimek wrote:
> >>emm, is not -uD something almost everybody does, but nobody should do?
> >>
> >>I had the same error - AFAIR reemerging java-config solved it.
>
> No, -uD is update deep, -UD is what you should NOT be doing.  the U
> means update only.  The difference is if say package-1.45 was marked
> stable and then found to be buggy, it gets masked in some way.  Then
> package-1.44 would be the most current stable package.  The U flag says
> not to go back to the 1.44 package.  On the other hand, the -u flag will
> "upgrade" to an older package if it is currently the newest unmasked or
> stable package.

-U is the OTHER flag you should never use ;)

If I remember correctly, a lot of time ago, it was said that you should not 
use -d, and must not use  -U  ....

but ok, everybody chooses his own poison.
I never do --deep updates, but occasionally -U update, because I am not 
willing to fiddle around with /etc/portage/package.mask /-.unmask for 
something that will be/should be marked stable in the next few days....
-- 
gentoo-amd64@gentoo.org mailing list



  parent reply	other threads:[~2005-10-17  8:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-17  1:14 [gentoo-amd64] Errors when doing an emerge -uD world Jamie Dobbs
2005-10-17  1:23 ` Hemmann, Volker Armin
2005-10-17  2:51   ` John C. Shimek
2005-10-17  7:54     ` Sebastian Redl
2005-10-17  8:09     ` Hemmann, Volker Armin [this message]
2005-10-17  1:28 ` Hagar
2005-10-17  1:39   ` Jamie Dobbs

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=200510171009.55681.volker.armin.hemmann@tu-clausthal.de \
    --to=volker.armin.hemmann@tu-clausthal.de \
    --cc=gentoo-amd64@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