On Tue, 07 Nov 2006 11:55:12 -0600, [EMAIL PROTECTED] wrote: > >> Attempting to start konqueror following an `update world' > > > > This is a meaningless statement, all you're saying is "I upgraded > > some packages, but I'm not telling you what they were". We'd need to > > know which packages were updated for this to be of any use. > > I'd hoped someone would have had the same or similar situation and > error before posted piles of data... so no not meaningless.
Yes, meaningless; update world means the packages on YOUR machine, matching YOUR arch and dependencies requires by YOUR use flags have been changed. No one can relate to that without knowing all those settings, or a simple list of the packages updated with "genlop --list --date yesterday" > > This is part of kdelibs, so you've probably either updated konqueror > > or kdelibs, re-emerge the other one. > > OK, checking on that. Kdelibs was updated > > Checking it out with emerge -vp konqueror I see the basic problem but > not really understanding what it means: > > [blocks B ] =kde-base/kdebase-3.5* (is blocking > kde-base/kcontrol-3.5.5, kde-base/libkonq-3.5.5, > kde-base/kdialog-3.5.5, kde-base/kfind-3.5.5, kde-base/kdesu-3.5.5, > kde-base/konqueror-3.5.5, kde-base/khelpcenter-3.5.5, > kde-base/kicker-3.5.5, kde-base/kdebase-kioslaves-3.5.5-r1, [snip] You're running the monolithic KDE ebuilds, so re-emerge kdebase. Incidentally, this is one of the situations where the split ebuilds really pay off, as you'd only have to recompile Konqueror rather than all the core KDE programs. -- Neil Bothwick RAM = Rarely Adequate Memory
signature.asc
Description: PGP signature
