unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@we.make.ritual.n0.is>
To: guix-devel@gnu.org
Subject: Re: [PATCH] gnunet-svn, gnunet-gtk-svn
Date: Sat, 30 Jul 2016 15:56:58 +0000	[thread overview]
Message-ID: <87eg6bf7at.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87invnf80e.fsf@we.make.ritual.n0.is>

ng0 <ng0@we.make.ritual.n0.is> writes:

> ng0 <ng0@we.make.ritual.n0.is> writes:
>
>> This is functional, but it suffers the same bug as the gnunet-0.10.1
>> package. I will write a gnunet-service for guix which will fix all
>> versions.
>> The expected behavior for installing gnunet is: create gnunet user with
>> gnunet group, create gnunet-dns group, build, install, configure through
>> gnunet-setup -c /path/to/gnunet.conf or setup without graphical tools,
>> add regular user to gnunet group, run gnunet stuff with regular user.
>>
>> You will experience the same stability with this svn as with 0.10.1 but
>> it will have the same broken behavior until I have fixed it.
>
> I am running a `gnunet-search avi' now to see how badly it needs to be
> fixed, but writing the service is in my own interest, so this will
> happen as the next contribution.

It is functional on that level, results come in after a while.
Whoever reviews, run this[0] instead and wait long enough. Maybe you even
need to run gnunet-setup before, adding the service would fix this a
bit.

[0]: `gnunet-search -V avi'


Off I go to openrc + guix service writing/debugging :)
-- 
♥Ⓐ  ng0
Current Keys: https://we.make.ritual.n0.is/ng0.txt
For non-prism friendly talk find me on http://www.psyced.org

  reply	other threads:[~2016-07-30 15:57 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 [this message]
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
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=87eg6bf7at.fsf@we.make.ritual.n0.is \
    --to=ng0@we.make.ritual.n0.is \
    --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).