1 |
On Wed, Feb 15, 2012 at 8:12 AM, Paul Hartman |
2 |
<paul.hartman+gentoo@×××××.com> wrote: |
3 |
> On Wed, Feb 15, 2012 at 10:00 AM, Allan Gottlieb <gottlieb@×××.edu> wrote: |
4 |
>> Nvidia-drivers fails with package collisions |
5 |
>> |
6 |
>> * Detected file collision(s): |
7 |
>> * |
8 |
>> * /usr/lib32/libnvidia-compiler.so |
9 |
>> * /usr/lib32/libcuda.so |
10 |
>> * /usr/lib32/libcuda.so.1 |
11 |
>> * /usr/lib64/libnvidia-compiler.so |
12 |
>> * /usr/lib64/libcuda.so |
13 |
>> * /usr/lib64/libcuda.so.1 |
14 |
>> |
15 |
>> But the owner of all these (via a symlink) is the currently installed |
16 |
>> version of nvidia-drivers. For example |
17 |
>> |
18 |
>> ajglap gottlieb # equery b /usr/lib32/libcuda.so.1 |
19 |
>> * Searching for /usr/lib32/libcuda.so.1 ... |
20 |
>> x11-drivers/nvidia-drivers-290.10-r1 (/usr/lib32/OpenCL/vendors/nvidia/libcuda.so.290.10) |
21 |
>> |
22 |
>> ajglap gottlieb # ls -l !$ |
23 |
>> ls -l /usr/lib32/libcuda.so.1 |
24 |
>> lrwxrwxrwx 1 root root 39 Feb 13 19:29 /usr/lib32/libcuda.so.1 -> OpenCL/vendors/nvidia/libcuda.so.290.10 |
25 |
>> |
26 |
>> So I don't really see the collision. Is the correct procedure |
27 |
>> |
28 |
>> 1. Copy the 12 files (both ends of the 6 links) someplace else |
29 |
>> 2. Get out of X |
30 |
>> 3. Try the emerge again |
31 |
>> |
32 |
>> thanks, |
33 |
>> allan |
34 |
> |
35 |
> Are the collisions with owned files, or just files that it doesn't |
36 |
> know about? i use protect-owned so it will overwrite any unknown |
37 |
> files, but abort on files owned by another known installed package. If |
38 |
> portage does not report them as owned by another package I think it's |
39 |
> usually safe to override (unless you have been installing things |
40 |
> outside of portage). |
41 |
> |
42 |
|
43 |
It may be related to all the OpenCL stuff that was just included in |
44 |
this last set of nvidia-driver packages. Possibly the ebuild hasn't |
45 |
handled the new stuff correctly? |
46 |
|
47 |
- Mark |