unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Langlois <pierre.langlois@gmx.com>
To: divoplade <d@divoplade.fr>
Cc: bug-guix@gnu.org, 47570-done@debbugs.gnu.org
Subject: bug#47570: libvirt still embeds full path to qemu-system in saved .xml files
Date: Tue, 06 Apr 2021 14:56:28 +0100	[thread overview]
Message-ID: <87mtub7bzn.fsf@gmx.com> (raw)
In-Reply-To: <93f528bfc35f533761637067f375db3ab09e6eb5.camel@divoplade.fr>

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


divoplade writes:

> Le lundi 05 avril 2021 à 19:45 +0100, Pierre Langlois a écrit :
>> Do you know at which guix commit this happened?  I'm wondering which
>> version of libvirt triggered this.  AFAICT, right now, if you create
>> a
>> fresh VM using gnome-boxes, it initializes the xml config with the
>> qemu
>> in /run/current-system/profile, which looks like the right thing to
>> do.
>
> I think my system did not auto-upgrade for some time because of a bug
> in org-html-export-to-html that broke one of my packages (the bug is,
> there’s an explicit comment to indicate a license for a script and that
> comment is not XHTML). I don’t know which commit did that, but the
> faulty system was between that commit and 24h before. Or there was
> another earlier problem, and I can’t help, sorry.
>
> You’re right, now that I upgraded it’s fixed.

Cool :-), closing the bug then!

Thanks,
Pierre


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 519 bytes --]

      reply	other threads:[~2021-04-06 13:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-02 20:41 bug#47570: libvirt still embeds full path to qemu-system in saved .xml files divoplade
2021-04-03 13:27 ` Maxime Devos
2021-04-05 18:45 ` Pierre Langlois
2021-04-06  6:48   ` divoplade
2021-04-06 13:56     ` Pierre Langlois [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=87mtub7bzn.fsf@gmx.com \
    --to=pierre.langlois@gmx.com \
    --cc=47570-done@debbugs.gnu.org \
    --cc=bug-guix@gnu.org \
    --cc=d@divoplade.fr \
    /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).