From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Raghav Gururajan <raghavgururajan@disroot.org>
Cc: 36634-done@debbugs.gnu.org
Subject: bug#36634: ATTENTION REQUIRED
Date: Thu, 25 Jul 2019 22:01:14 +0200 [thread overview]
Message-ID: <878sslj33p.fsf@nckx> (raw)
In-Reply-To: <1564083383.28412.1@submission.tobias.gr>
[-- Attachment #1: Type: text/plain, Size: 517 bytes --]
Tobias Geerinckx-Rice 写道：
>> Could anyone please update the libvirt package/service to this
>> latest
>> build?
>
> I will do so swiftly since I updated libvirt to the 'broken'
> version
> (although I never had any troubles like yours). Thank you for
> reporting this upstream.
I have applied ‘your’ patch in
41097b2dee9367974c6dd16ac1ba2ee945457237.
I'm closing this bug for now. However, could you update and
confirm that this actually solves the problem?
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-07-25 20:02 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 [this message]
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 ` bug#36634: (no subject) Brice Waegeneire
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=878sslj33p.fsf@nckx \
--to=me@tobias.gr \
--cc=36634-done@debbugs.gnu.org \
--cc=raghavgururajan@disroot.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.