the new portage version ignores statments like : RDEPEND="!gnome-base/gnome-core" which has caused us quite a lot of breakage with Gnome2 / Gnome 1 . supposedly it should say "blocked" and complain, but instead it allowes the update and overwrites the conflicting packages.
update. it works again after I did a emerge -pu world .. seems to be a cache desync here somewhere?
I don't know. I had the new version of portage (2.0.6) available masked for two days for developer testing. If you had tested it and reported these issues then, I could have looked into them before releasing 2.0.7.
OK, I was able to track down the problem. Portage 2.0.8 (masked -- committing now) should fix the issue for you. I do appreciate the bug report; apologies for the mini-rant.
Would actually have tried it if I haden't been completely overloaded with other stuff at that time. Most of those included an 8 hour powerfailure, a brokem Network accesspoint (thunder) and a Gnome 2 release :) Will test 2.0.8.
