| 1 |
On Wed, Feb 15, 2012 at 2:04 PM, Mark Knecht <markknecht@×××××.com> wrote: |
| 2 |
> On Wed, Feb 15, 2012 at 11:43 AM, Mark Knecht <markknecht@×××××.com> wrote: |
| 3 |
>> On Wed, Feb 15, 2012 at 11:11 AM, Allan Gottlieb <gottlieb@×××.edu> wrote: |
| 4 |
>>> On Wed, Feb 15 2012, Mark Knecht wrote: |
| 5 |
>>> |
| 6 |
>>>> On Wed, Feb 15, 2012 at 8:12 AM, Paul Hartman |
| 7 |
>>>> <paul.hartman+gentoo@×××××.com> wrote: |
| 8 |
>>>>> On Wed, Feb 15, 2012 at 10:00 AM, Allan Gottlieb <gottlieb@×××.edu> wrote: |
| 9 |
>>>>>> Nvidia-drivers fails with package collisions |
| 10 |
>>>>>> |
| 11 |
>>>>>> * Detected file collision(s): |
| 12 |
>>>>>> * |
| 13 |
>>>>>> * /usr/lib32/libnvidia-compiler.so |
| 14 |
>>>>>> * /usr/lib32/libcuda.so |
| 15 |
>>>>>> * /usr/lib32/libcuda.so.1 |
| 16 |
>>>>>> * /usr/lib64/libnvidia-compiler.so |
| 17 |
>>>>>> * /usr/lib64/libcuda.so |
| 18 |
>>>>>> * /usr/lib64/libcuda.so.1 |
| 19 |
>>>>>> |
| 20 |
>>>>>> But the owner of all these (via a symlink) is the currently installed |
| 21 |
>>>>>> version of nvidia-drivers. For example |
| 22 |
>>>>>> |
| 23 |
>>>>>> ajglap gottlieb # equery b /usr/lib32/libcuda.so.1 |
| 24 |
>>>>>> * Searching for /usr/lib32/libcuda.so.1 ... |
| 25 |
>>>>>> x11-drivers/nvidia-drivers-290.10-r1 (/usr/lib32/OpenCL/vendors/nvidia/libcuda.so.290.10) |
| 26 |
>>>>>> |
| 27 |
>>>>>> ajglap gottlieb # ls -l !$ |
| 28 |
>>>>>> ls -l /usr/lib32/libcuda.so.1 |
| 29 |
>>>>>> lrwxrwxrwx 1 root root 39 Feb 13 19:29 /usr/lib32/libcuda.so.1 -> OpenCL/vendors/nvidia/libcuda.so.290.10 |
| 30 |
>>>>>> |
| 31 |
>>>>>> So I don't really see the collision. Is the correct procedure |
| 32 |
>>>>>> |
| 33 |
>>>>>> 1. Copy the 12 files (both ends of the 6 links) someplace else |
| 34 |
>>>>>> 2. Get out of X |
| 35 |
>>>>>> 3. Try the emerge again |
| 36 |
>>>>>> |
| 37 |
>>>>>> thanks, |
| 38 |
>>>>>> allan |
| 39 |
>>>>> |
| 40 |
>>>>> Are the collisions with owned files, or just files that it doesn't |
| 41 |
>>>>> know about? i use protect-owned so it will overwrite any unknown |
| 42 |
>>>>> files, but abort on files owned by another known installed package. If |
| 43 |
>>>>> portage does not report them as owned by another package I think it's |
| 44 |
>>>>> usually safe to override (unless you have been installing things |
| 45 |
>>>>> outside of portage). |
| 46 |
>>>>> |
| 47 |
>>>> |
| 48 |
>>>> It may be related to all the OpenCL stuff that was just included in |
| 49 |
>>>> this last set of nvidia-driver packages. Possibly the ebuild hasn't |
| 50 |
>>>> handled the new stuff correctly? |
| 51 |
>>>> |
| 52 |
>>>> - Mark |
| 53 |
>>> |
| 54 |
>>> Perhaps. All the files are links to files with OpenCL in the path. |
| 55 |
>>> |
| 56 |
>>> But I am still unsure what to do. |
| 57 |
>>> I mentioned a three step procedure above. |
| 58 |
>>> Perhaps best is to do nothing and hope -r2 will come along and |
| 59 |
>>> install cleanly. |
| 60 |
>>> Toward that end should I file a bug at bugs.gentoo.org? |
| 61 |
>>> |
| 62 |
>>> allan |
| 63 |
>>> |
| 64 |
>> |
| 65 |
>> I'm emerging the package here to investigate whether it's a global |
| 66 |
>> issue or maybe just one you are seeing. I'll get back to you on that. |
| 67 |
>> |
| 68 |
>> I think if it was me (and it may be in 10 minutes...) then I'd drop |
| 69 |
>> into the console, emerge -C nvidia-drivers, probably run |
| 70 |
>> revdep-rebuild or something to look for files that aren't owned, |
| 71 |
>> remove them by hand, and then emerge nvidia-drivers back in. |
| 72 |
>> |
| 73 |
>> - Mark |
| 74 |
> |
| 75 |
> OK, here I saw the same file list but the emerge didn't fail. The |
| 76 |
> installation told me it was overwriting the files because no one |
| 77 |
> claimed to own them. |
| 78 |
> |
| 79 |
> That's some sort of ebuild problem and I'd agree that a bug should be filed. |
| 80 |
|
| 81 |
That behavior can be controlled by your FEATURES settings |
| 82 |
(collision-protect or protect-owned) and optionally modified further |
| 83 |
in make.conf by COLLISION_IGNORE. |
Archives