| 1 |
On Thursday 12 November 2009 16:43:15 Mark Knecht wrote: |
| 2 |
> So on one machine yesterday I did emerge -DuN @world which then |
| 3 |
> suggested the need for emerge @preserved-rebuild which I did over |
| 4 |
> night. This morning it was finished but suggested the need for a |
| 5 |
> second emerge @preserved-rebuild. As I don't need the machine right |
| 6 |
> now I kicked it off and will check it again later but I'm wondering |
| 7 |
> why in the world it needs to do this twice, compiling 52 packages the |
| 8 |
> first time and 50 packages the second time where most of the packages |
| 9 |
> in the first list were in the second list? |
| 10 |
> |
| 11 |
> Is this setting up for an endless loop? |
| 12 |
> |
| 13 |
> Most of the packages were part of Gnome or XFCE4. |
| 14 |
|
| 15 |
I've been answering this question a lot lately :-) |
| 16 |
|
| 17 |
Almost invariably it's an automagic dependency where the offending package is |
| 18 |
not in DEPEND. If you have been through the cycle at least once, it is safe to |
| 19 |
delete /var/lib/portage/preserved_libs_registry and continue on your way. |
| 20 |
|
| 21 |
A later revdep-rebuild will sort out any (highly unlikely) remaining issues |
| 22 |
|
| 23 |
-- |
| 24 |
alan dot mckinnon at gmail dot com |
Archives