For more information about Blocked Packages, please refer to the following
section of the Gentoo Linux x86 Handbook (architecture is irrelevant):

http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked

!!! The following installed packages are masked:
- perl-core/ExtUtils-MakeMaker-6.20 (masked by: package.mask)
/usr/portage/profiles/package.mask:
# Torsten Veller <tove@gentoo.org> (27 May 2009)
# PDEPEND on more dual life modules that also install
# into scriptdir
# Masked until perl-5.8.8-r6 is stable for amd64 and x86

Thanks for your help. I agree that this is most likely fixed with changes in /etc/portage but it's not that I've forgotten, the problem is that I don't know how to figure out which packages to keyword or unkeyword or mask or unmask, etc.

See this line? It means that kdelibs is pulling qt-webkit-4.5.1. This shouldnt happen and it (probably) means that you haven't keyworded qt-webkit so it is pulling the stable 4.5.1 instead of 4.5.2

Try adding x11-libs/qt-webkit on /etc/portage/package.keywords file

Thanks. I probably would have never figured that out by myself.

I'm actually trying to stay with the stable branch as much as possible. I've noticed that I have to keep keywording more and more packages to get emerge to work but I'm almost never removing packages from the keyword file(s). For example, here are (what I think are) the kde-4/qt-4 and related packages I've added so far to keep emerge happy:

I agree about having to live with the pain. I think the invention of /etc/portage/package.* was a great leap forward but the point I was trying to make before is that there seems to be a flaw the makes using mixed software branches more complicated than the page you linked to would make it seem.

The problem I keep running into is that if I want to run a mixed system then I have to keep adding more and more packages to the keyword file(s) in order to get around blockages to emerge -uDN world. But there seems to be no mechanism (that I know of) that removes packages from the keyword file(s). So a mixed system gradually evolves into an ~unstable system.

The only way to go back that I know of is to follow the suggestion you made in jest of cleaning out the keyword file(s) and then add back in the packages that still need to be keyworded.

My current situation is a good example. In a previous post I listed all of the new packages I needed to keyword in order to keep emerge -uDN world happy which includes a lot of qt stuff. But now if I look at the new recommended kde-4.2 keyword file, all that unstable qt stuff is no longer needed.

Perhaps all that is needed is a tool that automatically removes entries from the keyword file(s) when they are no longer needed.

My current situation is a good example. In a previous post I listed all of the new packages I needed to keyword in order to keep emerge -uDN world happy which includes a lot of qt stuff. But now if I look at the new recommended kde-4.2 keyword file, all that unstable qt stuff is no longer needed.

Of course. You dont need unstable qt-4.5.2 to run kde4. You can use the stable 4.5.1

Please pardon the repetition....I am running into this issue right now... I believe I have read this whole thread carefully, and tried to do the things that are recommended, but I am still experiencing blocks. I am running testing (~x86). I hope someone can help quickly because I want to reboot my system, but I'm afraid KDE won't work properly when it comes back up, and this is my work machine I want to be confident that it'll be ok when I restart. I don't want to do a whole emerge world if I can avoid it... is it the only way? Here's my basic info:

Please pardon the repetition....I am running into this issue right now... I believe I have read this whole thread carefully, and tried to do the things that are recommended, but I am still experiencing blocks. I am running testing (~x86). I hope someone can help quickly because I want to reboot my system, but I'm afraid KDE won't work properly when it comes back up, and this is my work machine I want to be confident that it'll be ok when I restart. I don't want to do a whole emerge world if I can avoid it... is it the only way? Here's my basic info:

(My posts keep getting truncated! What the heck is going on here? When I look at "preview", it looks fine, but then after I post, it's truncated. Anybody else seeing this?)

Long posts are silently truncated, this becomes especially obvious for posts containing significant numbers of BBCode tags or characters which are expanded in some way to encode them for storage. This is, presently, the expected behavior.

qt-3 is not split, so it's not a meta but a monolithic package, which you absolutely need for kde3. Only Qt4 has been split._________________"Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF