On Sun, 27 Mar 2011 22:09:15 +0000, CJoeB wrote:

> >> ACCEPT_KEYWORDS="~x86" emerge --update --deep world  
> > That will update every package to the latest ~x86 version, and cause
> > them all to downgrade again the next time you emerge world. As this
> > includes packages that are both critical and hate being downgraded,
> > like glibc, this is a really bad idea.
> >
> > You would have to really hate someone to want to put them through
> > this.  
> 
> Okay, I see your point.  I don't make a habit of unmasking packages.  
> However, as stated in my previous message, I can't get past the kde
> ~x86 updates to update other packages that might have valid stable
> updates. I don't care if kde updates to an unstable version, I would
> just like to get past it so I can see what else needs to be updated.
> 

The command suggested would only switch KDE to testing, it would switch
your whole system, a step that is extremely difficult to reverse without
reinstallation.

If you can't find a culprit in /etc/portage, as already suggested, try
renaming that directory and running .emerge -puDN world to see if it still
happens. Stable packages shouldn't depend on testing packages so either
you have a setting in /etc/portage that is causing this or a buggy ebuild.

Another possibility is that this is caused by something in an overlay,
which you can quickly test by commenting out any OVERLAY or layman
entries in make.conf.


-- 
Neil Bothwick

I can't walk on water, but I can stagger on alcohol.