On Thu, Nov 12, 2009 at 6:58 AM, Alan McKinnon <alan.mckin...@gmail.com> wrote: > On Thursday 12 November 2009 16:43:15 Mark Knecht wrote: >> So on one machine yesterday I did emerge -DuN @world which then >> suggested the need for emerge @preserved-rebuild which I did over >> night. This morning it was finished but suggested the need for a >> second emerge @preserved-rebuild. As I don't need the machine right >> now I kicked it off and will check it again later but I'm wondering >> why in the world it needs to do this twice, compiling 52 packages the >> first time and 50 packages the second time where most of the packages >> in the first list were in the second list? >> >> Is this setting up for an endless loop? >> >> Most of the packages were part of Gnome or XFCE4. > > I've been answering this question a lot lately :-) > > Almost invariably it's an automagic dependency where the offending package is > not in DEPEND. If you have been through the cycle at least once, it is safe to > delete /var/lib/portage/preserved_libs_registry and continue on your way. > > A later revdep-rebuild will sort out any (highly unlikely) remaining issues > > -- > alan dot mckinnon at gmail dot com
Thanks Alan. I always tend to do a revdep-rebuild -i anyway. Not sure if it's required but old habits die hard. Cheers, Mark
