all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 36476-close@debbugs.gnu.org
Subject: bug#36476: [PATCH] gnu: Add anonip.
Date: Tue, 9 Jul 2019 13:24:16 +0200	[thread overview]
Message-ID: <2e57b964-9f99-36bb-5a98-083fceccb15c@crazy-compilers.com> (raw)
In-Reply-To: <877e9032jx.fsf@nckx>


[-- Attachment #1.1: Type: text/plain, Size: 1052 bytes --]

Tobias,

Thanks for your review. Committed as
582de58c69bd46385196e26434951e1e2d5f32f2

> Thanks!  This should nicely replace some (probably buggy) ad-hoc code
> of mine :-)

:-)

> +    (inputs
>> +     `(("python-3" ,python-3)))
>
> I'm surprised: the python-build-system should take care of this. Does
> the package fail without it?  How?

You are right, this is not required. I copied this without questioning
from some other python application (don't remember which one).


>> +Depending on your webserver software, the log entries may directly
>> get piped
>> +to Anonip or read via a FIFO (named pipe).  Thus the unmasked IP
>> addresses 
>
> ‘read from’.

I rephrased this into "Depending on your Web server, the log entries may
be piped to Anonip directly
or via a FIFO (named pipe)."  This emphases on piping


-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2019-07-09 11:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-02 14:20 [bug#36476] [PATCH] gnu: Add anonip Hartmut Goebel
2019-07-02 14:59 ` Tobias Geerinckx-Rice
2019-07-09 11:24   ` Hartmut Goebel [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2e57b964-9f99-36bb-5a98-083fceccb15c@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=36476-close@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.