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

Diederik de Haas didi.debian at cknow.org
Thu Aug 4 19:29:24 UTC 2016


Hi Luca,

On donderdag 4 augustus 2016 13:35:55 CEST Luca Boccassi wrote:
> Control: severity -1 important
> 
> On Thu, 2016-08-04 at 02:03 +0200, Diederik de Haas wrote:
> > On donderdag 4 augustus 2016 01:52:28 CEST Andreas Beckmann wrote:
> > > are you upgrading from locally built packages that were built from SVN
> > > some time ago?
> > 
> > I am indeed.

It was the build I reported on pkg-nvidia-devel at lists.alioth.debian.org with 
title 'Building newer releases from SVN':
http://lists.alioth.debian.org/pipermail/pkg-nvidia-devel/2016-July/
013221.html

> 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'

> Given the workaround, and the fact that the packages with that problem
> were never actually uploaded in the repos, I'll downgrade the severity.

I'm also fine with downgrading it more as I now consider this a user error.

> However, I'm happy to add a fix for the next upload to facilitate users
> of locally built packages.

It sounds like a good candidate to add to the wiki on the building from source 
section. Thus severity wishlist sounds fine too ;-)

> I think a simple "Replaces: nvidia-vulkan-icd" on nvidia-vulkan-common
> should do the trick.

If it improves the package, then it sounds like a good addition even though 
this was a user error.

> Kind regards,
> Luca Boccassi

Cheers,
  Diederik



More information about the pkg-nvidia-devel mailing list