public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "John C. Shimek" <jcshimek@mn.rr.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Errors when doing an emerge -uD world
Date: Sun, 16 Oct 2005 21:51:01 -0500	[thread overview]
Message-ID: <43531195.6080802@mn.rr.com> (raw)
In-Reply-To: <200510170323.26637.volker.armin.hemmann@tu-clausthal.de>

>
>
>>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. 

I think the biggest problem, I could be wrong thoug, is that usually 
when packages get remasked like that and upgrades go backwards, it is a 
security problem.  And even that seems to be uncommon.  I have not ever 
seen one of my packages go backwards but I could have missed one or two.
-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2005-10-17  2:49 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 [this message]
2005-10-17  7:54     ` Sebastian Redl
2005-10-17  8:09     ` Hemmann, Volker Armin
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=43531195.6080802@mn.rr.com \
    --to=jcshimek@mn.rr.com \
    --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