nvidia-cuda-dev conflicts with nvidia-experimental-*

Hi there

If anyone wants to work around this while waiting on the fix, as I needed to do, this is how I did it. What you would do is download the attached patches file to a folder that you create and run the set of commands below. Run the commands one by one in case something doesn't work.

Note the patches are not complete; they are only for a very specific proble - you need to edit them if e.g. you are using nvidia-experimental-304.
Also, take care. If things are different on your system it may not work.

Regardses
Damien

sudo apt-get install build-essential fakeroot dpkg-dev ubuntu-dev-tools #possibly the last one is unnecessary

mkdir nvidia_cuda_fix #where we will be working

cd nvidia_cuda_fix #download the patch files to here - patches_cuda_work_with_310_1210.tar.gz

apt-get source nvidia-cuda-toolkit #get the source for the package - you will build it - this is the source with all the additional ubuntu/debian bits

tar -xvzvf patches_cuda_work_with_310_1210.tar.gz #unzip the patches I have provided in the attachment and which you downloaded

patch nvidia-cuda-toolkit_4.2.9-1ubuntu1.dsc nvidia-cuda-toolkit_4.2.9-1ubuntu1.dsc.patch.20121220 #adds nvidia-experimental-310 to list of dependencies

dpkg-source -x nvidia-cuda-toolkit_4.2.9-1ubuntu1.dsc # I am not sure what this does exactly... - extracts the source package - I think actually this is already done by apt-get, but anyway

cd nvidia-cuda-toolkit-4.2.9/ #go to where things are going to be built

patch debian/control ../control.patch.20121220 #adds nvidia-experimental-310 to list of dependencies

dpkg-buildpackage -rfakeroot -b #compile the stuff we are going to install

cd .. #it has put the deb files in the parent dir (our working dir)

sudo apt-get install gcc-4.4 g++-4.4 libthrust-dev opencl-headers # some random dependencies of the built packages - you may need more here and rerun the below line untill things work if dependencies weren't satisfied on your system

sudo dpkg --install *deb # install it and see it break

Status changed to 'Confirmed' because the bug affects multiple users.

This bug was fixed in the package nvidia-cuda-toolkit - 5.0.35-4

---------------
nvidia-cuda-toolkit (5.0.35-4) experimental; urgency=low

  [ Graham Inggs ]
  * Ubuntu: Build-Depend/Depend on nvidia-experimental-* (LP: #1092259).

  [ Andreas Beckmann ]
  * Ubuntu: Override libcuda.so.1 dependencies via shlibs.local to support
    installing with nvidia-experimental-* while building against
    nvidia-current. (Closes: #700621)

 -- Andreas Beckmann <email address hidden> Sat, 16 Feb 2013 15:58:28 +0100

Hello Graeme, or anyone else affected,

Accepted nvidia-cuda-toolkit into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/4.0.17-3ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Graeme, or anyone else affected,

Accepted nvidia-cuda-toolkit into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/4.2.9-1ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Is there an ETA on seeing this in proposed? I still don't see it today.

I've accepted the binaries now and they're on their way in within the next hour or so.

In raring can it also suppport nvidia-310-* and nvida-313-*?

Looks good to me now in quantal, but I second the suggestion that it support all nvidia driver releases in raring.

nvidia-cuda-toolkit 4.0.17-3ubuntu0.1 installs fine for me in Precise with only nvidia-experimental-310 installed, nvidia-current is no longer being installed as well.

@Graeme: A new bug was opened for Raring:
https://bugs.launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/+bug/1162945

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

This bug was fixed in the package nvidia-cuda-toolkit - 4.0.17-3ubuntu0.1

---------------
nvidia-cuda-toolkit (4.0.17-3ubuntu0.1) precise-proposed; urgency=low

  * Backport the following changes from 5.0.35-4 in Raring so that
    nvidia-cuda-toolkit can also be built and installed on systems with
    nvidia-experimental installed and without depending on and recommending
    nvidia-current.
    - debian/{control,rules}: Use substvars for the names of the libcuda1 and
      nvidia-libopencl1 packages.
    - Build-Depend/Depend on nvidia-current | nvidia-current-updates |
      nvidia-experimental-*. instead of libcuda1 and nvidia-libopencl1.
      (LP: #950963)
    - Override libcuda.so.1 dependencies via shlibs.local to support
      installing with nvidia-experimental-* while building against
      nvidia-current. (LP: #1092259)
 -- Graham Inggs <email address hidden> Wed, 20 Feb 2013 13:23:19 +0200

This bug was fixed in the package nvidia-cuda-toolkit - 4.2.9-1ubuntu1.1

---------------
nvidia-cuda-toolkit (4.2.9-1ubuntu1.1) quantal-proposed; urgency=low

  * Backport the following changes from 5.0.35-4 in Raring so that
    nvidia-cuda-toolkit can also be built and installed on systems with
    nvidia-experimental installed and without depending on and recommending
    nvidia-current. (LP: #1092259).
    - debian/{control,rules}: Use substvars for the names of the libcuda1 and
      nvidia-libopencl1 packages.
    - Build-Depend/Depend on nvidia-current | nvidia-current-updates |
      nvidia-experimental-*. instead of libcuda1 and nvidia-libopencl1.
    - Override libcuda.so.1 dependencies via shlibs.local to support
      installing with nvidia-experimental-* while building against
      nvidia-current.
 -- Graham Inggs <email address hidden> Wed, 20 Feb 2013 10:55:42 +0200