unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 27855@debbugs.gnu.org
Subject: [bug#27855] [PATCH] gnu: Add rsync service.
Date: Thu, 31 Aug 2017 00:59:36 +0100	[thread overview]
Message-ID: <20170831005936.79ac99e3@cbaines.net> (raw)
In-Reply-To: <87d17kh9n8.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 499 bytes --]

On Fri, 25 Aug 2017 01:40:43 +0300
Oleg Pykhalov <go.wigust@gmail.com> wrote:
> I tried to apply all your suggestion, but I really don't know why
> 'rsync-configuration-user' is ignored (it's always set to "rsyncd").
> 
> I use 'pk' to debug this, but still confused.

For comparing strings in Guile, I think its more reliable to use equal?
rather than eq?, and I think this is the cause of the issues with the
validation. I don't get validation failures when using (equal? user
"root").

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

  reply	other threads:[~2017-08-31  0:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27 22:01 [bug#27855] [PATCH] gnu: Add rsync service Oleg Pykhalov
2017-07-27 22:22 ` [bug#27855] ERROR: rsync rsync://localhost/files Oleg Pykhalov
2017-07-28  6:45 ` [bug#27855] [PATCH] services: rsync: Fix invalid gid nobody Oleg Pykhalov
2017-07-28 22:17 ` [bug#27855] [PATCH] gnu: Add rsync service Christopher Baines
2017-07-29 11:03   ` Oleg Pykhalov
2017-07-29 11:55     ` Christopher Baines
2017-08-03 15:20       ` Oleg Pykhalov
2017-08-03 15:29         ` Oleg Pykhalov
2017-08-03 15:33         ` Christopher Baines
2017-08-03 16:20           ` Oleg Pykhalov
2017-08-03 16:34             ` Oleg Pykhalov
2017-08-10  7:18             ` Christopher Baines
2017-08-10 18:21               ` Christopher Baines
2017-08-10 18:56                 ` Oleg Pykhalov
2017-08-11 19:28                   ` Oleg Pykhalov
2017-08-12  6:59                     ` Christopher Baines
2017-08-12 13:13                       ` Oleg Pykhalov
2017-08-12 17:46                         ` Christopher Baines
2017-08-12 20:19                           ` Oleg Pykhalov
2017-08-12 21:19                             ` Christopher Baines
2017-08-19 20:34                               ` Oleg Pykhalov
2017-08-19 22:19                                 ` Christopher Baines
2017-08-24 22:40                                   ` Oleg Pykhalov
2017-08-30 23:59                                     ` Christopher Baines [this message]
2017-08-31 13:04                                       ` Ludovic Courtès
2017-09-16 22:44                                         ` Oleg Pykhalov
2017-09-16 22:49                                           ` Oleg Pykhalov
2017-09-17  8:40 ` [bug#27855] Status: " Oleg Pykhalov
2017-09-18  6:20 ` [bug#27855] " Christopher Baines
2017-09-23  1:47   ` Oleg Pykhalov
2017-09-23  2:38     ` Oleg Pykhalov
2017-09-23 20:12     ` bug#27855: " Christopher Baines

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=20170831005936.79ac99e3@cbaines.net \
    --to=mail@cbaines.net \
    --cc=27855@debbugs.gnu.org \
    --cc=go.wigust@gmail.com \
    /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).