From: Brice Waegeneire <brice@waegenei.re>
To: 36634@debbugs.gnu.org
Subject: bug#36634: (no subject)
Date: Thu, 19 Mar 2020 10:06:35 +0000 [thread overview]
Message-ID: <76c4a36a5e46a15e32ecdc95d8189182@waegenei.re> (raw)
In-Reply-To: <255adc32694ef0c22fb789b1eea66a243cffb649.camel@disroot.org>
Hello,
> Chris Marusich <cmmarusich@gmail.com> writes:
>> I see the patch was incorporated into Guix master in commit
>> aa1f0896fb15a0bdcc5474839c8afdbb2520d603. That is good, and I think
>> this issue can be resolved. If nobody follows up in a few days' time,
>> let's close the bug report.
>
> I created 38032 on guix-patches and Ludo’ applied them.
Looks like this issue can be closed.
I can't reproduce the bug. Upstream fixed it in libvirt 5.10, so
we'll be able to remove Miguel's patch when we upgrade libvrit.
Brice.
prev parent reply other threads:[~2020-03-19 10:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-13 5:06 bug#36634: Virtual Machine Manager (virt-manager) Raghav Gururajan
2019-07-14 12:42 ` Efraim Flashner
2019-07-14 21:21 ` Raghav Gururajan
2019-07-21 17:23 ` Christopher Baines
2019-07-21 21:42 ` Raghav Gururajan
2019-09-23 4:14 ` Chris Marusich
2019-09-23 4:30 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-05 5:41 ` Chris Marusich
2019-10-10 8:55 ` Chris Marusich
2019-07-25 9:46 ` bug#36634: ATTENTION REQUIRED Raghav Gururajan
2019-07-25 19:36 ` Tobias Geerinckx-Rice
2019-07-25 20:01 ` Tobias Geerinckx-Rice
2019-07-26 3:51 ` bug#36634: Raghav Gururajan
2019-07-26 3:47 ` bug#36634: Raghav Gururajan
2019-09-08 18:14 ` bug#36634: Virtual Machine Manager (virt-manager) Christopher Baines
2019-10-21 14:46 ` Miguel Arruga Vivas
2019-10-27 9:37 ` Miguel Arruga Vivas
2019-11-07 8:44 ` Chris Marusich
2019-11-08 0:53 ` Miguel Arruga Vivas
2020-03-19 10:06 ` Brice Waegeneire [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=76c4a36a5e46a15e32ecdc95d8189182@waegenei.re \
--to=brice@waegenei.re \
--cc=36634@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).