I have -debug in my make.conf USE Regardless, all KDE packages are being built with debug USE flag set *on*. This causes an *enormous* amount of spam to be sent to the .xsession-errors log file. Compounded w/other bugs elsewhere (kdebugdialog doesn't actually work, and kdm forcefully replaces .xsession-errors from a symlink to a regular file at login) people are forced to logout/login to clear out a >1GB file every few days. All the extra debug code paths may also be contributing to a slower feel in the desktop. I've tested with both debug not mentioned in my USE flags, and with -debug explicitly added. In both cases after emerge debug was reported as on for the packages merged. I removed debug from the IUSE in the meta class and that had no affect. I am not sure where it's happening/who is doing it.
Please post the output of "emerge -uDpvN kde-meta" and USE="-debug" emerge -uDpvN kde-meta"
Created attachment 254679 [details] output from "emerge -uDpvN kde-meta" (In reply to comment #1) > Please post the output of "emerge -uDpvN kde-meta" and USE="-debug" emerge > -uDpvN kde-meta" > I've attached the log file. Only one was needed because the outputs were identical. That makes it look like it's going to work. However, for example, with kmail: # emerge -p kmail These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] kde-base/kmail-4.4.7 USE="-debug%" And after the merge: # eix -I kmail [I] kde-base/kmail Available versions: (4.4) 4.4.5 ~4.4.6 4.4.7 {aqua debug +handbook kdeenablefinal kdeprefix +kontact} Installed versions: 4.4.7(4.4)(18:19:25 11/16/10)(handbook kontact -aqua -kdeenablefinal -kdeprefix) Homepage: http://www.kde.org/ Description: KMail is the email component of Kontact, the integrated personal information manager of KDE. debug is enabled anyways.
Your attachment includes the following: ('installed', '/', 'x11-libs/qt-multimedia-4.6.2', 'nomerge') pulled in by x11-libs/qt-multimedia required by world You have some blocks preventing the merge because of the above. Please run the following command "grep x11-libs/qt /var/lib/portage/world*" to check how many qt packages you added to the world file. You'll have to remove them from the world file to solve the conflicts. About the eix output, I don't recall the exact meaning, so I'd rather go with the emerge output that shows the debug use flag is disabled. Just to double check, post also the output of "grep debug /var/db/cache/*/*/USE"
Created attachment 254681 [details] output from "emerge -uDpvN kde-meta" I removed all the x11-libs/qt-* stuff from the world file then ran them both again. Again, both were the same. Also: # grep debug /var/db/pkg/*/*/USE came up empty. Does this mean that my KDE is installed w/o the debug USE flag, and it's an eix display bug? Several comments received on related KDE bugs (related to what's showing up in the .xsession-error file) indicate that much of that output should only be possible from a debug build of KDE.
(In reply to comment #4) > Also: > # grep debug /var/db/pkg/*/*/USE > > came up empty. > > Does this mean that my KDE is installed w/o the debug USE flag, and it's an eix > display bug? Seems like it. You're down to 1 unsolved block now: ('ebuild', '/', 'sys-libs/libraw1394-2.0.4', 'merge') pulled in by sys-libs/libraw1394 required by ('installed', '/', 'dev-libs/pwlib-1.10.10-r2', 'nomerge') sys-libs/libraw1394 required by ('installed', '/', 'media-video/ffmpeg-0.6', 'nomerge') >=sys-libs/libraw1394-1.2.0 required by ('installed', '/', 'media-libs/libdc1394-2.1.2', 'nomerge') (and 2 more) ('installed', '/', 'media-libs/libdc1394-1.2.1', 'nomerge') pulled in by media-libs/libdc1394:1 required by ('installed', '/', 'dev-libs/pwlib-1.10.10-r2', 'nomerge') You may need to update or keyword a more recent version of dev-libs/pwlib.
Created attachment 254693 [details] output from "emerge -uDpvN kde-meta" emerge -aC media-libs/libdc1394-1.2.1 and then updating libraw1394 cleared out the blockage The resulting output attached. Also, I just realized what brain fart I had. The eix output is correct--the first list is the list of *possible* USE flags, not the USE as installed.
My bad. Sorry.
