From: someone13574 <someone13574@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] intel_icd.i686.json installed from incorrect package
Date: Fri, 10 Feb 2023 17:14:52 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42189@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
New issue by someone13574 on void-packages repository
https://github.com/void-linux/void-packages/issues/42189
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.10_1 x86_64-musl GenuineIntel uptodate rrnFFF
### Package(s) Affected
mesa-vulkan-intel, mesa-vulkan-intel-32bit
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
The `/usr/share/vulkan/icd.d/intel_icd.i686.json ` manifest file would be install along side the shared library it references.
### Actual behaviour
The `/usr/share/vulkan/icd.d/intel_icd.i686.json` file is installed with the `mesa-vulkan-intel` package while it references the shared library `/usr/lib32/libvulkan_intel.so`, a library that is installed with the `mesa-vulkan-intel-32bit` package. This package is not available on musl systems.
### Steps to reproduce
1. Run `vulkaninfo | grep ERROR` on a system without `mesa-vulkan-intel-32bit` installed
2. Observe the error loading `/usr/lib32/libvulkan_intel.so`
next reply other threads:[~2023-02-10 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 16:14 someone13574 [this message]
2023-03-09 15:44 ` abenson
2023-06-26 14:25 ` adigitoleo
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42189@inbox.vuxu.org \
--to=someone13574@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).