On Wed, Feb 15 2012, Mark Knecht wrote: > On Wed, Feb 15, 2012 at 8:12 AM, Paul Hartman > <paul.hartman+gen...@gmail.com> wrote: >> On Wed, Feb 15, 2012 at 10:00 AM, Allan Gottlieb <gottl...@nyu.edu> wrote: >>> Nvidia-drivers fails with package collisions >>> >>> * Detected file collision(s): >>> * >>> * /usr/lib32/libnvidia-compiler.so >>> * /usr/lib32/libcuda.so >>> * /usr/lib32/libcuda.so.1 >>> * /usr/lib64/libnvidia-compiler.so >>> * /usr/lib64/libcuda.so >>> * /usr/lib64/libcuda.so.1 >>> >>> But the owner of all these (via a symlink) is the currently installed >>> version of nvidia-drivers. For example >>> >>> ajglap gottlieb # equery b /usr/lib32/libcuda.so.1 >>> * Searching for /usr/lib32/libcuda.so.1 ... >>> x11-drivers/nvidia-drivers-290.10-r1 >>> (/usr/lib32/OpenCL/vendors/nvidia/libcuda.so.290.10) >>> >>> ajglap gottlieb # ls -l !$ >>> ls -l /usr/lib32/libcuda.so.1 >>> lrwxrwxrwx 1 root root 39 Feb 13 19:29 /usr/lib32/libcuda.so.1 -> >>> OpenCL/vendors/nvidia/libcuda.so.290.10 >>> >>> So I don't really see the collision. Is the correct procedure >>> >>> 1. Copy the 12 files (both ends of the 6 links) someplace else >>> 2. Get out of X >>> 3. Try the emerge again >>> >>> thanks, >>> allan >> >> Are the collisions with owned files, or just files that it doesn't >> know about? i use protect-owned so it will overwrite any unknown >> files, but abort on files owned by another known installed package. If >> portage does not report them as owned by another package I think it's >> usually safe to override (unless you have been installing things >> outside of portage). >> > > It may be related to all the OpenCL stuff that was just included in > this last set of nvidia-driver packages. Possibly the ebuild hasn't > handled the new stuff correctly? > > - Mark
Perhaps. All the files are links to files with OpenCL in the path. But I am still unsure what to do. I mentioned a three step procedure above. Perhaps best is to do nothing and hope -r2 will come along and install cleanly. Toward that end should I file a bug at bugs.gentoo.org? allan
