On Wed, Dec 2, 2009 at 3:10 PM, Mark Knecht <[email protected]> wrote: > Hi all, > This came up maybe a month ago on some of my machines. Now I'm > updating the MythTV network of 3 dedicated machines and I'm seeing the > same thing. The machines are clean with emerge -DuN @world but stuck > in what appears to be an endless loop of @preserved-rebuild's. I've > been through the loop 3 times with no changes any time. > > Before I do what I did last time (which was just erase the > preserved_libs_registry file by hand) I figured I'd see what a better > way to handle this is. Last time I think Neil suggested that multiple > passes through emerge @preserved-rebuild would eliminate this but I've > done 3 passes so far and it appears stuck. > > Possibly I should emerge -C e2fsprogs-libs and then do another > emerge -DuN @world? > > Other ideas? > > Same exact results on 3 machines... > > Thanks, > Mark
No quick answers from the list so I tried: emerge -C e2fsprogs-libs emerge -DuN @world? revdep-rebuild -i and now the preserved-rebuild info is gone. myth12 ~ # emerge -p @preserved-rebuild emerge: 'preserved-rebuild' is an empty set emerge: no targets left after set expansion myth12 ~ # So I guess it's fixed. Right? Right... Over and out, Mark
