From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qemu/libvirt: virt-aa-helper refuses to create AppArmor VM profiles when using QEMU provided OVMF images from /usr/share/qemu
Date: Thu, 19 Aug 2021 00:20:49 +0200 [thread overview]
Message-ID: <20210818222049.o2JCkWzt0aI-OQG3GExCM05_ewMkRg8LBngYZQcAlx8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32562@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/32562#issuecomment-901467601
Comment:
This sounds exactly like the issue in #31904, is there a reason why you created a new issue instead of commenting there?
Your second solution sounds better to me, but we will need to make sure that moving the files will not conflict with #29074. There are more qualified people to decide this.
cc @Hoshpak - maintainer of libvirt and qemu
next prev parent reply other threads:[~2021-08-18 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 14:38 [ISSUE] " sernkut
2021-08-18 22:20 ` paper42 [this message]
2021-08-18 22:39 ` sernkut
2021-08-18 22:39 ` [ISSUE] [CLOSED] " sernkut
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=20210818222049.o2JCkWzt0aI-OQG3GExCM05_ewMkRg8LBngYZQcAlx8@z \
--to=paper42@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).