From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108359] amdgpu-pro rpm packages cyclical dependencies
Date: Mon, 15 Oct 2018 00:25:19 +0000 [thread overview]
Message-ID: <bug-108359-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 6504 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108359
Bug ID: 108359
Summary: amdgpu-pro rpm packages cyclical dependencies
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu-pro
Assignee: dri-devel@lists.freedesktop.org
Reporter: ilmostro7@gmail.com
Using the latest amdgpu-pro packages from
https://www.amd.com/en/support/kb/release-notes/rn-prorad-lin-18-30 for RHEL7,
it seems that a number of the packages and their "*-pro" counterparts are
constantly reported as upgrades for the other. This means that every time an
attempt is made to upgrade the system, e.g. vulkan-amdgpu is listed as an
upgrade that obsoletes vulkan-amdgpu-pro, and vice versa.
# yum upgrade
Loaded plugins: aliases, changelog, copr, langpacks, priorities, product-id,
protectbase, ps, search-disabled-repos, subscription-manager, versionlock
0 packages excluded due to repository protections
Resolving Dependencies
--> Running transaction check
---> Package vulkan-amdgpu.x86_64 0:18.30-641594.el7 will be obsoleting
---> Package vulkan-amdgpu-pro.x86_64 0:18.30-641594.el7 will be obsoleted
--> Finished Dependency Resolution
Dependencies Resolved
=================================================================================================================================================================================================================================================================================
Package Arch
Version
Repository
Size
=================================================================================================================================================================================================================================================================================
Installing:
vulkan-amdgpu x86_64
18.30-641594.el7
amdgpu-pro-local
10 M
replacing vulkan-amdgpu-pro.x86_64 18.30-641594.el7
Transaction Summary
=================================================================================================================================================================================================================================================================================
Install 1 Package
Total download size: 10 M
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : vulkan-amdgpu-18.30-641594.el7.x86_64
1/2
Erasing : vulkan-amdgpu-pro-18.30-641594.el7.x86_64
2/2
Verifying : vulkan-amdgpu-18.30-641594.el7.x86_64
1/2
Verifying : vulkan-amdgpu-pro-18.30-641594.el7.x86_64
2/2
Installed:
vulkan-amdgpu.x86_64 0:18.30-641594.el7
Replaced:
vulkan-amdgpu-pro.x86_64 0:18.30-641594.el7
Complete!
[19:24][20181014-1]# yum upgrade
Loaded plugins: aliases, changelog, copr, langpacks, priorities, product-id,
protectbase, ps, search-disabled-repos, subscription-manager, versionlock
0 packages excluded due to repository protections
Resolving Dependencies
--> Running transaction check
---> Package vulkan-amdgpu.x86_64 0:18.30-641594.el7 will be obsoleted
---> Package vulkan-amdgpu-pro.x86_64 0:18.30-641594.el7 will be obsoleting
--> Finished Dependency Resolution
Dependencies Resolved
=================================================================================================================================================================================================================================================================================
Package Arch
Version
Repository
Size
=================================================================================================================================================================================================================================================================================
Installing:
vulkan-amdgpu-pro x86_64
18.30-641594.el7
amdgpu-pro-local
4.5 M
replacing vulkan-amdgpu.x86_64 18.30-641594.el7
Transaction Summary
=================================================================================================================================================================================================================================================================================
Install 1 Package
Total download size: 4.5 M
Is this ok [y/d/N]:
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 7913 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-10-15 0:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 0:25 bugzilla-daemon [this message]
2018-12-04 16:39 ` [Bug 108359] amdgpu-pro rpm packages cyclical dependencies bugzilla-daemon
2019-02-27 22:10 ` 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-108359-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox