unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon South <simon@simonsouth.net>
To: 44435@debbugs.gnu.org
Subject: [bug#44435] [PATCH 1/1] services: Add transmission-daemon service.
Date: Sat, 07 Nov 2020 09:12:44 -0500	[thread overview]
Message-ID: <87mtzt5k83.fsf@simonsouth.net> (raw)
In-Reply-To: <7630c2a18eded24bbfc66d45b353a9faab400d93.1604429058.git.simon@simonsouth.net> (Simon South's message of "Wed, 4 Nov 2020 07:40:06 -0500")

Simon South <simon@simonsouth.net> writes:
> +(define (transmission-daemon-activation config)
> +  "Return the Transmission Daemon activation GEXP for CONFIG."
> +  (let ((owner (getpwnam %transmission-daemon-user))

This call to "getpwnam" should be executed on the build side, not the
host side.

Also, since Ludovic's commit ca465a9c8454, configuring a system that
uses this service type issues

  gnu/services/file-sharing.scm:736:9: warning: importing module (guix config) from the host

which I assume is a problem.

I'm working on an update that addresses these things.

-- 
Simon South
simon@simonsouth.net




  reply	other threads:[~2020-11-07 14:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-04 12:37 [bug#44435] [PATCH 0/1] services: Add Transmission Daemon Simon South
2020-11-04 12:40 ` [bug#44435] [PATCH 1/1] services: Add transmission-daemon service Simon South
2020-11-07 14:12   ` Simon South [this message]
2020-11-08 18:06 ` [bug#44435] [PATCH v2 0/1] services: Add Transmission Daemon Simon South
2020-11-08 18:06   ` [bug#44435] [PATCH v2 1/1] services: Add transmission-daemon service Simon South
2020-11-18 22:39   ` [bug#44435] [PATCH v2 0/1] services: Add Transmission Daemon Ludovic Courtès
2020-11-19  0:35     ` Simon South
2020-12-05 15:27 ` [bug#44435] [PATCH v3 " Simon South
2020-12-05 15:27   ` [bug#44435] [PATCH v3 1/1] services: Add transmission-daemon service Simon South
2021-02-12  7:15   ` bug#44435: [PATCH v3 0/1] services: Add Transmission Daemon 宋文武

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=87mtzt5k83.fsf@simonsouth.net \
    --to=simon@simonsouth.net \
    --cc=44435@debbugs.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).