On Montag, 28. Juli 2008, Alan E. Davis wrote: > On Mon, Jul 28, 2008 at 4:55 PM, Volker Armin Hemmann < > > [EMAIL PROTECTED]> wrote: > > On Montag, 28. Juli 2008, Andrey Falko wrote: > > > To eliminate the first factor do: emerge -e world. > > > > no. Just no. > > For what it's worth, I started emerge -e system quite some time ago. It > stops about 1/2 way through on glib. Apparently this is common. I > started it up again as "emerge -e system --skipfirst". How bad of an idea > was that? I think about 200 out of about 350 pkgs have been rebuilt. > > I'll halt this and rebuild dbus again. Etc/ > > > > The second > > > factor can be eliminated by downgrading to firefox2. If it is a > > > firefox3 problem then the bug report would go to firefox developers. > > It does affect firefox 2 also. All users except root. All gecko browsers, > I guess (all firefox, and epiphany---didnt' try galeon). > > > just re-emerge dbus and/or revdep-rebuilt should be enough. Or that > > 'preserved-libs' stuff. > > I don't qet it about preserved-libs. THerefore I haven't done anything > about any of the messages. I don't understand the messages, exactly what > would happen? Would I be building the same app with the same old lib or > with the new lib? I need to find something in the docs, but haven't seen > anything yet.
http://r0bertz.blogspot.com/2008/06/portage-22-preserve-libs-features.html the problem with it (a friend run into it - maybe the have fixed it in the meantime)if you do an emerge -e system/world while the old stuff is still there, some apps and libs will link against the old stuff. Thus the whole exercise will be a waste of time and energy.
