From: Andreas Enge <andreas@enge.fr>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnunet-svn, gnunet-gtk-svn
Date: Tue, 2 Aug 2016 00:21:35 +0200 [thread overview]
Message-ID: <20160801222135.GA9924@solar> (raw)
In-Reply-To: <87lh0ikl95.fsf@we.make.ritual.n0.is>
On Sun, Jul 31, 2016 at 01:08:54PM +0000, ng0 wrote:
> This was another failing test, someone before me reported it and
> therefore I have no bugreport to point to. I consider it superfluous
> work to fix 0.10.1 (the (define-public gnunet)) now that work towards
> 0.10.2 release happens. Tests might or might not change, so the svn
> version is more logical to fix and report bugs on.
So maybe it may make sense to wait for 0.10.2 instead of adding packages
based on unreleased commits? In the meantime, you could work with upstream
to iron out test failures, and when 0.10.2 comes out, you might have a
working gnunet package.
Andreas
next prev parent reply other threads:[~2016-08-01 22:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 15:11 [PATCH] gnunet-svn, gnunet-gtk-svn ng0
2016-07-30 15:41 ` ng0
2016-07-30 15:56 ` ng0
2016-07-31 13:08 ` ng0
2016-08-01 14:34 ` ng0
2016-08-01 19:01 ` Catonano
2016-08-01 19:42 ` ng0
2016-08-01 22:21 ` Andreas Enge [this message]
2016-08-02 8:27 ` ng0
2016-08-02 10:30 ` ng0
2016-08-02 13:05 ` Catonano
2016-08-02 14:09 ` ng0
2016-08-02 14:57 ` Catonano
2016-08-02 15:31 ` ng0
2016-08-03 11:45 ` ng0
2016-08-03 12:05 ` Catonano
2016-08-03 21:10 ` Andreas Enge
2016-08-06 12:54 ` ng0
2016-08-06 23:43 ` ng0
2016-08-07 8:21 ` ng0
2016-08-18 13:27 ` Catonano
2016-08-18 14:15 ` ng0
2016-08-20 11:17 ` ng0
2016-08-20 12:04 ` ng0
2016-08-27 0:06 ` Catonano
2016-08-27 13:20 ` ng0
2016-08-19 7:13 ` Alex Kost
2016-08-19 7:42 ` ng0
2016-08-25 11:36 ` ng0
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=20160801222135.GA9924@solar \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=ng0@we.make.ritual.n0.is \
/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).