Bug 110960 - Non-existent alternative dependencies in some deb packages
Summary: Non-existent alternative dependencies in some deb packages
Status: RESOLVED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu-pro (show other bugs)
Version: unspecified
Hardware: Other All
: medium trivial
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 110956
  Show dependency tree / graph
 
Reported: 2019-06-22 02:27 UTC by Andrew Shark
Modified: 2019-07-30 08:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Andrew Shark 2019-06-22 02:27:09 UTC 
19.20-812932 release for Ubuntu
mesa-amdgpu-va-drivers_18.3.0-812932_amd64.deb and mesa-amdgpu-va-drivers_18.3.0-812932_i386.deb have such dependencies:
libva1-amdgpu | libva2-amdgpu | libva1 | libva2

mesa-amdgpu-vdpau-drivers_18.3.0-812932_amd64.deb and mesa-amdgpu-vdpau-drivers_18.3.0-812932_i386.deb have such:
libvdpau1-amdgpu | libvdpau1

But libva1-amdgpu, libva2-amdgpu, libvdpau1-amdgpu do not exist neither in ubuntu repos, nor provided by bundled archive.

Is there any special intent to add such alternative dependencies?
Comment 1 Eric Engestrom 2019-06-22 15:46:21 UTC 
Ubuntu packaging issue; this needs to be reported to Ubuntu instead.
Comment 2 Eric Engestrom 2019-06-22 17:57:18 UTC 
TIL AMD does its support via our bugzilla...
Comment 3 Jeremy Newton 2019-07-29 20:05:13 UTC 
Thanks for the input.

This is more of a "in case we need them" situation.

I believe our RHEL driver includes these packages since they do not come in the standard RHEL repos, but we don't have the limitation with Ubuntu, or at least not right now.
Comment 4 Michel Dänzer 2019-07-30 08:44:37 UTC 
FWIW, it doesn't make much sense to have libva1* as alternatives for libva2*. Different SONAME means incompatible ABI, so something linked against the libva2 ABI generally isn't expected to work with something providing the libva1 ABI.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.