From: phrdina <phrdina@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] qemu: using incorrect datadir /usr/lib when build qemu package
Date: Thu, 09 Jul 2020 14:24:16 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23495@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
New issue by phrdina on void-packages repository
https://github.com/void-linux/void-packages/issues/23495
Description:
### System
* xuname:
Void 5.7.7_1 x86_64 x86_64 AuthenticAMD uptodate rF
* package:
qemu-5.0.0_2
### Expected behavior
edk2 json firmware files installed by qemu package should be in `/usr/share/qemu/firmware/` directory.
### Actual behavior
They are currently installed in `/usr/lib/qemu/firmware/` directory which is incorrect. If you check QEMU documentation for the firmware json files [https://git.qemu.org/?p=qemu.git;a=blob;f=docs/interop/firmware.json;hb=HEAD](url) it has an explicit list of directories where the firmware json files should be and libvirt looks for this files only at these directories in order to provide the installed firmwares to users or to management applications like virt-manager.
### Steps to reproduce the behavior
`xbps-install qemu`
`xbps-query -f qemu`
next reply other threads:[~2020-07-09 12:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 12:24 phrdina [this message]
2020-07-11 15:25 ` sgn
2020-07-11 15:27 ` sgn
2020-07-12 23:21 ` phrdina
2020-07-19 10:57 ` pandom79
2020-07-20 9:27 ` phrdina
2020-07-20 9:32 ` pandom79
2020-07-20 14:00 ` pandom79
2020-07-21 7:44 ` pandom79
2020-07-22 13:05 ` phrdina
2020-07-22 13:11 ` pandom79
2020-09-14 7:11 ` [ISSUE] [CLOSED] " Hoshpak
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-23495@inbox.vuxu.org \
--to=phrdina@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).