<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=GBK">
</head>
<body>
On Mon, 6 Jan 2025 17:02:57 +0100 Andrea Bolognani <eof@kiyuko.org>
wrote:<br>
> Control: tags -1 fixed-upstream pending<br>
> <br>
> On Mon, Jan 06, 2025 at 08:07:46PM +0800, zhangdandan wrote:<br>
> > Dear maintainers,<br>
> > <br>
> > We need to Cherry-pick upstream patch to run loongarch64
VMs when AppArmor<br>
> > is enabled.<br>
> > The commit from upstream is
<a class="moz-txt-link-freetext" href="https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/thread/IU7KHMVCORZP4E525RQI7A6BZARXN5CB/">https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/thread/IU7KHMVCORZP4E525RQI7A6BZARXN5CB/</a>.<br>
> > <br>
> > You can also consider the patch we attached.<br>
> > And the libvirt 10.10.0-4+loong64 source package was
compiled successfully<br>
> > on my local ENV.<br>
> > <br>
> > Would it be possible to include the attached patch in
the next upload?<br>
> > You opinions are welcome.<br>
> <br>
> Thanks for the patch.<br>
> <br>
> However, the next upstream release will be tagged in less
than two<br>
> weeks, so it doesn't really make sense to prepare another
upload<br>
> before then. We'll just pick up this fix with the upcoming
rebase,<br>
> same as #1089607.<br>
<br>
</eof@kiyuko.org>Okay. I agree with what you said.<br>
The next Release version of the upstream Libvirt may be released in
less than two weeks.<br>
This commit [1] will be include in the next Release version.<br>
Look forward to Debian libvirt's next upload.<br>
<br>
[1]:<a class="moz-txt-link-freetext" href="https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/thread/IU7KHMVCORZP4E525RQI7A6BZARXN5CB/">https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/thread/IU7KHMVCORZP4E525RQI7A6BZARXN5CB/</a><br>
<br>
Best regards,<br>
Dandan Zhang<br>
</body>
</html>