From: Andreas Enge <andreas@enge.fr>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org, Daniel Pimentel <d4n1@member.fsf.org>
Subject: Re: Network-Manager test fail
Date: Thu, 18 Feb 2016 20:52:33 +0100 [thread overview]
Message-ID: <20160218195233.GA3445@solar> (raw)
In-Reply-To: <87egccxo9x.fsf@netris.org>
Hi Mark,
On Tue, Feb 16, 2016 at 05:51:06PM -0500, Mark H Weaver wrote:
> Without seeing your test-suite.log, I'm not sure if these are the same
> failures I'm getting, but network-manager consistently fails to build
> for me as well.
>
> Here's a patch I've used to enable building on my machine. Maybe it
> works for you too.
would it not make sense to push the patch then?
Andreas
prev parent reply other threads:[~2016-02-18 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 23:41 Network-Manager test fail Daniel Pimentel
2016-02-15 1:53 ` Leo Famulari
2016-02-15 10:03 ` Efraim Flashner
2016-02-16 22:51 ` Mark H Weaver
2016-02-18 19:52 ` Andreas Enge [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=20160218195233.GA3445@solar \
--to=andreas@enge.fr \
--cc=d4n1@member.fsf.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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).