FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 02-15-2012, 03:00 PM
Allan Gottlieb
 
Default unclear package collisions in nvidia-drivers-295.20-r1

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
 
Old 02-15-2012, 03:12 PM
Paul Hartman
 
Default unclear package collisions in nvidia-drivers-295.20-r1

On Wed, Feb 15, 2012 at 10:00 AM, Allan Gottlieb <gottlieb@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).
 
Old 02-15-2012, 03:28 PM
Mark Knecht
 
Default unclear package collisions in nvidia-drivers-295.20-r1

On Wed, Feb 15, 2012 at 8:12 AM, Paul Hartman
<paul.hartman+gentoo@gmail.com> wrote:
> On Wed, Feb 15, 2012 at 10:00 AM, Allan Gottlieb <gottlieb@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
 
Old 02-15-2012, 06:09 PM
Allan Gottlieb
 
Default unclear package collisions in nvidia-drivers-295.20-r1

On Wed, Feb 15 2012, Paul Hartman wrote:

> On Wed, Feb 15, 2012 at 10:00 AM, Allan Gottlieb <gottlieb@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 ran equery belongs and each of those files are owned
by nvidia-drivers, the package that is being emerged.

They are of course owned by the current version -295.10-r1.
I am trying to merge the new version -295.20-r1.

thanks
allan
 
Old 02-15-2012, 06:11 PM
Allan Gottlieb
 
Default unclear package collisions in nvidia-drivers-295.20-r1

On Wed, Feb 15 2012, Mark Knecht wrote:

> On Wed, Feb 15, 2012 at 8:12 AM, Paul Hartman
> <paul.hartman+gentoo@gmail.com> wrote:
>> On Wed, Feb 15, 2012 at 10:00 AM, Allan Gottlieb <gottlieb@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
 

Thread Tools




All times are GMT. The time now is 12:59 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org