From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110958] Mentioning 32 bit OS support in Release page
Date: Sat, 22 Jun 2019 01:47:35 +0000 [thread overview]
Message-ID: <bug-110958-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1003 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110958
Bug ID: 110958
Summary: Mentioning 32 bit OS support in Release page
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: enhancement
Priority: medium
Component: DRM/AMDgpu-pro
Assignee: dri-devel@lists.freedesktop.org
Reporter: ashark@linuxcomp.ru
19.20-812932 release for Ubuntu
Release page
https://www.amd.com/en/support/kb/release-notes/rn-rad-lin-19-20-unified says
that it supports ubuntu x86_64, but actually it can be installed on ubuntu x86.
In case you do not want to support ubuntu x86, then why include several 32-bit
meta packages? For example, there are amdgpu-pro-hwe:i386 and amdgpu-pro-lib32.
You could drop amdgpu-pro-hwe:i386 then.
Or is that made intentionally?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2382 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 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 1:47 bugzilla-daemon [this message]
2019-06-22 15:41 ` [Bug 110958] Mentioning 32 bit OS support in Release page bugzilla-daemon
2019-06-24 8:59 ` 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-110958-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.