On 09/05/2014 23:34, gottl...@nyu.edu wrote: > On Fri, May 09 2014, gottl...@nyu.edu wrote: > >> On Fri, May 09 2014, Alan McKinnon wrote: >> >>> There's a brute force method. All the nvidia files listed below are now >>> orphaned, so you should be able to delete them and let revdep-rebuild >>> fix anything remaining. You also have stuffs from emul-linux in there, >>> so I'd suggest this: >>> >>> unmerge emul-linux-x86-opengl >>> delete orphaned files >>> revdep-rebuild and let it do what it wants >>> remerge emul-linux-x86-opengl back >>> >> I see. This encouraged me to look at >> /var/lib/portage/preserved_libs_registry, whose contents is >> >> "x11-drivers/nvidia-drivers:0": [ >> "x11-drivers/nvidia-drivers-334.21-r3", >> "12161", >> [ >> "/usr/lib64/libnvidia-glcore.so.334.21", >> "/usr/lib64/libnvidia-tls.so.334.21", >> "/usr/lib32/libnvidia-glsi.so.334.21", >> "/usr/lib32/opengl/nvidia/lib/libGL.so.334.21", >> "/usr/lib64/libnvidia-glsi.so.334.21", >> "/usr/lib32/opengl/nvidia/lib/libEGL.so.334.21", >> "/usr/lib64/opengl/nvidia/lib/libGL.so.334.21", >> "/usr/lib32/libnvidia-tls.so.334.21", >> "/usr/lib64/opengl/nvidia/lib/libEGL.so.334.21", >> "/usr/lib32/libnvidia-glcore.so.334.21", >> "/usr/lib64/opengl/nvidia/lib/libGL.so.1", >> "/usr/lib64/opengl/nvidia/lib/libEGL.so.1", >> "/usr/lib32/opengl/nvidia/lib/libGL.so.1", >> "/usr/lib32/opengl/nvidia/lib/libEGL.so.1" >> ] >> ] >> } >> >> So I guess this means that all the orphans come from nvidia-drivers. >> So I am initially not unmerging/remerging emul-linux-x86. >> That is my plan will be >> >> move orphaned files listed above to a holding area >> let revdep-rebuild do its thing >> wait 30 days >> delete the holding bin >> >> Thanks for explaining. >> allan > > Before I mess up let me ask if the contents of preserved_libs_registry > shown above will be cleaned by the emerges triggered by revdep-rebuild > or if I am supposed to modify that file myself when I remove the > orphans. > > thanks, > allan
I'm not entirely certain how portage maintains preserved_libs_registry and when it gets modified (I suspect the exact answer has changed over time) so my recommendation is to leave the file alone unless you are forced to modify it. I've done that a few times in the past to fix issues like you ar dealing with - it's a rather blunt weapon though. Having said that, it's not especially dangerous. preserved_libs_registry is really just a bunch of flags of stuff to be rebuilt, so if you do mess it up, a round of emerge world && revdep-rebuild gets things consistent again, it just takes some time and cpu cycles -- Alan McKinnon alan.mckin...@gmail.com
