From: "Ludovic Courtès" <ludo@gnu.org>
To: Allan Adair <allan@adair.no>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: libvirt: A potential problem in the package and looking for guidance
Date: Mon, 23 May 2022 17:28:07 +0200 [thread overview]
Message-ID: <8735h046bc.fsf@gnu.org> (raw)
In-Reply-To: <8881f77c80bbc6fc4950ed64e2aef77f5a32c16f.camel@adair.no> (Allan Adair's message of "Wed, 18 May 2022 13:43:48 +0200")
Hi,
Allan Adair <allan@adair.no> skribis:
> File "/gnu/store/g2x37cxh2ag5h66f0p9zaz9pkz2vcvgg-python-libvirt-
> 7.9.0/lib/python3.9/site-packages/libvirt.py", line 1353, in create
> raise libvirtError('virDomainCreate() failed')
> libvirt.libvirtError: '/usr/libexec/qemu-bridge-helper' is not a suitable
> bridge helper: No such file or directory
>
>
> Because the package is searching specifically for "/usr/libexec/qemu-
> bridge-helper", I think this is a bug in the package definition. "/usr"
> should probably be a prefix from the store, right?
>
> Any comments or suggestions?
Presumably that “/usr/libexec/qemu-bridge-helper” reference is
hard-coded in the source. The solution in situations like this is to
replace it (using ‘substitute*’) by the absolute file name of the
corresponding program in /gnu/store.
(substitute* "some/file.py"
(("/usr/libexec/qemu-bridge-helper")
(search-input-file inputs "/bin/qemu-bridge-helper")))
HTH!
Ludo’.
next prev parent reply other threads:[~2022-05-23 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 11:43 libvirt: A potential problem in the package and looking for guidance Allan Adair
2022-05-23 15:28 ` Ludovic Courtès [this message]
2022-05-23 16:06 ` Maxime Devos
2022-05-23 19:44 ` Allan Adair
2022-05-23 20:35 ` Maxime Devos
-- strict thread matches above, loose matches on Subject: below --
2022-05-20 15:50 Rene Saavedra
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=8735h046bc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=allan@adair.no \
--cc=guix-devel@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).