Bug#833405: nvidia-vulkan-icd: Missing conflict: /usr/share/vulkan/icd.d/nvidia_icd.json provided by 2 packages

[Diederik de Haas]

The following is the result of bug 833405, but it isn't related to the bug IMO 
therefor only sending it to the ML.

On donderdag 4 augustus 2016 21:29:24 CEST Diederik de Haas wrote:
> > To fix your immediate problem running "apt-get install -f" and then
> > upgrade again should be sufficient.
> 
> I just did an 'aptitude update' and 'aptitude safe-upgrade' and it
> installed/ configured the packages just fine even though there were no new
> nvidia/vulkan packages with the new updates. Thus I didn't even have to use
> '-f'

That turned out to be an incorrect statement. It didn't show any nvidia 
packages being configured as it didn't 'process' them. But (today) I noticed 
that 7 packages weren't upgraded and they were all related to nvidia.

In order to get to a clean state I rebooted into recovery mode and purge all 
nvidia/vulkan/cuda packages from my system, rebooted and tried to install them 
again. But what I then got looked a bit strange to me. 

I wanted to directly install the driver from experimental using either 
'aptitude install nvidia-driver -t experimental' and 'aptitude install nvidia-
driver/experimental', but it constantly wanted to install packages from either 
armhf or i386 or both as solutions. My system is primarily amd64, but I do 
have both armhf and i386 added as foreign architectures. 
Here's what I get when trying to install nvidia-driver from sid:

# aptitude install nvidia-driver
Reading package lists...
Building dependency tree...
Reading state information...
Reading extended state information...
Initializing package states...
Writing extended state information...
Building tag database...
The following NEW packages will be installed:
  gcc-6-base:i386{a} glx-alternative-mesa{a} glx-alternative-nvidia{a} glx-
diversions{a} libc6:i386{a} libegl-nvidia0{a} libegl-nvidia0:i386{a} libegl1-
glvnd-nvidia{a} libegl1-glvnd-nvidia:i386{a} libgcc1:i386{a} libgl1-nvidia-
glx{a} libgl1-nvidia-glx:i386{a} libgldispatch0-nvidia{a} libgldispatch0-
nvidia:i386{a} libgles-nvidia1{a} libgles-nvidia1:i386{a} libgles-nvidia2{a} 
libgles-nvidia2:i386{a} libgles1-glvnd-nvidia{a} libgles1-glvnd-nvidia:i386{a} 
libgles2-glvnd-nvidia{a} libgles2-glvnd-nvidia:i386{a} libglx-nvidia0{a} 
libglx-nvidia0:i386{a} libglx0-glvnd-nvidia{a} libglx0-glvnd-nvidia:i386{a} 
libnvidia-cfg1{a} libnvidia-cfg1:i386{a} libnvidia-eglcore{a} libnvidia-
eglcore:i386{a} libnvidia-glcore{a} libnvidia-glcore:i386{a} libnvidia-ml1{a} 
libopengl0-glvnd-nvidia{a} libopengl0-glvnd-nvidia:i386{a} libx11-6:i386{a} 
libxau6:i386{a} libxcb1:i386{a} libxdmcp6:i386{a} libxext6:i386{a} nvidia-
alternative{a} nvidia-driver nvidia-driver-bin{a} nvidia-driver-libs{a} 
nvidia-driver-libs:i386{a} nvidia-driver-libs-i386:i386{a} nvidia-installer-
cleanup{a} nvidia-kernel-common{a} nvidia-kernel-dkms{a} nvidia-kernel-
support{a} nvidia-legacy-check{a} nvidia-modprobe{a} nvidia-persistenced{a} 
nvidia-support{a} nvidia-vdpau-driver{a} update-glx{a} xserver-xorg-video-
nvidia{a} 
0 packages upgraded, 57 newly installed, 0 to remove and 0 not upgraded.
Need to get 46.8 MB of archives. After unpacking 196 MB will be used.
Do you want to continue? [Y/n/?] Abort.

Is it expected/normal that it wants to install a (whole) bunch of packages 
from i386?
I have experienced this type of behavior before (bug 805132) and I'm 
reasonably sure it would still not cause any harm and it may still be an issue 
with aptitude. But I do find it odd that I only see this behavior with nvidia 
packages and I prefer not to install packages I won't need (even though they'd 
only take up some disk space).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/attachments/20160807/392c7b94/attachment.sig>