From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Minikube broken because libvirtd has unconventional socket names (temporary fix included)
Date: Fri, 10 Jan 2020 00:02:17 +0100 [thread overview]
Message-ID: <20200109230217._XOLlpEM2TmcaadU5fxzRUbMYwtcFYwH1wRvoi0bkv8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18133@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 369 bytes --]
New comment by leonardlorenz on void-packages repository
https://github.com/void-linux/void-packages/issues/18133#issuecomment-572796703
Comment:
I really don't see another solution outside of symlinking libvirt-sock to libvirt-sockd in the post_install() function of libvirt's template. Someone more versed with libvirt and packaging should take a look if possible.
next prev parent reply other threads:[~2020-01-09 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 9:47 [ISSUE] Minikube broken because libvirtd has unconventional socket names voidlinux-github
2020-01-09 23:02 ` voidlinux-github [this message]
2020-01-10 9:31 ` Minikube broken because libvirtd has unconventional socket names (temporary fix included) voidlinux-github
2020-02-25 10:01 ` [ISSUE] [CLOSED] " leonardlorenz
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=20200109230217._XOLlpEM2TmcaadU5fxzRUbMYwtcFYwH1wRvoi0bkv8@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).