Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libvirt: fix deadlock for musl
Date: Fri, 06 Nov 2020 18:33:02 +0100	[thread overview]
Message-ID: <20201106173302.UEQxLFBxvHD9TIlKCzv-XnjgcgoxdeXrL67-Y44YP60@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25905@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 751 bytes --]

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/25905#issuecomment-723206179

Comment:
I just pushed `libvirt-6.9.0_1`, and I was able to successfully interact with `libvirtd` on `x86_64-musl` by launching a Windows domain and then using `virt-viewer` to interact with it. Please try to reproduce your issue on this new version, document the steps if it is still reproducible, and rebase the patches.

There seems to be some contention on the mailing list and your linked issue about whether this patch is correct, and they were not upstreamed for this release. If they are not still obsolete, we'll have to weigh the apparent benefits of the patch against the obvious resistance from upstream.

  parent reply	other threads:[~2020-11-06 17:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 22:45 [PR PATCH] " sirn
2020-10-26 22:52 ` [PR PATCH] [Updated] " sirn
2020-11-06 17:33 ` ahesford [this message]
2020-11-08 10:27 ` sirn
2020-11-08 10:36 ` sirn
2020-11-17 20:38 ` Logarithmus
2020-11-17 20:38 ` Logarithmus
2020-11-17 20:40 ` Logarithmus
2020-12-23 17:35 ` gch1p
2021-01-02  3:41 ` [PR PATCH] [Closed]: " ahesford

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=20201106173302.UEQxLFBxvHD9TIlKCzv-XnjgcgoxdeXrL67-Y44YP60@z \
    --to=ahesford@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).