Dale wrote:
Dmitry S. Makovey wrote:
On November 25, 2008, Nikos Chantziaras wrote:
I decided to give portage 2.1.6_rc1 a try. Now it wants to upgrade my
KDE3 to KDE4. I never unmasked or keyworded any KDE4 stuff. Any
options other than removing portage 2.1.6_rc1 again?
1st of all, I'm running 2.2.x versions of portage and never had KDE4 magically
unmasked. You'd better check your setup. I do realize that 2.2.x is not
2.1.6_rc1, but what I mean - it must be either a bug in portage or your
setup. Find where the problem originates. Do you have ~arch KDE3 ? I suppose
you don't run ~arch branch, right?
I am using portage-2.2_rc15 and I have unstable KDE 3 but nothing KDE
4. I actually tested KDE 4 once and had to unmask all the KDE 4 stuff
to get it.
I agree, there is something fishy about his/her setup. I think that if
this happened to anyone else, someone would have spoke up by now. I'll
sync in a little bit and test mine to be sure tho.
No, not unmasked but keyworded. We've figured it out by now. It was
because KDE4 was getting masked automatically by EAPI2 which stable
portage doesn't support. As soon as portage was upgraded, no masking
anymore due to EAPI and hence KDE4 got pulled-in.
