From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110960] Non-existent alternative dependencies in some deb packages
Date: Sat, 22 Jun 2019 02:27:09 +0000 [thread overview]
Message-ID: <bug-110960-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1134 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110960
Bug ID: 110960
Summary: Non-existent alternative dependencies in some deb
packages
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: trivial
Priority: medium
Component: DRM/AMDgpu-pro
Assignee: dri-devel@lists.freedesktop.org
Reporter: ashark@linuxcomp.ru
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?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2419 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-06-22 2:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 2:27 bugzilla-daemon [this message]
2019-06-22 15:41 ` [Bug 110960] Non-existent alternative dependencies in some deb packages bugzilla-daemon
2019-06-22 15:46 ` bugzilla-daemon
2019-06-22 17:57 ` bugzilla-daemon
2019-07-29 20:05 ` bugzilla-daemon
2019-07-30 8:44 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-110960-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.