Bug#755513: nvidia-opencl-dev: binary conflict with ocl-icd-libopencl1

[Graham Inggs]

On 22/07/2014 14:59, Tomasz Rybak wrote:
> Why did nvidia-cuda-toolkit tried to install nvidia-opencl-dev
> when you had ocl-icd-libopencl1 installed?

 From what I can tell, because of the missing 'conflicts'.

> $ apt-cache show nvidia-cuda-toolkit
> Package: nvidia-cuda-toolkit
> Version: 5.5.22-4
> Installed-Size: 44180
> Maintainer: Debian NVIDIA Maintainers
> <pkg-nvidia-devel at lists.alioth.debian.org>
> Architecture: amd64
> Depends: nvidia-profiler (= 5.5.22-4), nvidia-cuda-dev (= 5.5.22-4),
> nvidia-opencl-dev (= 5.5.22-4) | opencl-dev, gcc, g++, libc6 (>= 2.3.4),
> libgcc1 (>= 1:4.1.1), libnvvm2 (>= 5.5), libstdc++6 (>= 4.1.1)
>
> ocl-icd-opencl-dev depends on ocl-icd-libopencl1, and ocl-icd-libopencl1
> conflicts with libopencl1, preventing other packages with libOpenCL.so
> from being installed.

But nvidia-opencl-dev conflicts with opencl-dev, and ocl-icd-liopencl1 
conflicts with libopencl1.
There is no explicit conflict between each other.

> Can you provide what you were doing?

I was simply trying to reproduce the similar problem that occurs in 
Ubuntu, see LP: #1311975, LP: #1325526 and LP: #1341072.
So I did:
apt-get install ocl-icd-libopencl1
followed by:
apt-get install nvidia-cuda-toolkit

> I have situation similar to described by you (ocl-icd-opencl-dev and
> ocl-icd-libopencl1 and nvidia-cuda-toolkit) and did not have any
> troubles - I even prepare and test PyCUDA and PyOpenCL packages
> on such a setup.

If you install ocl-icd-opencl-dev *after* nvidia-cuda-toolkit, the 
problem does not occur.