unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org, guix-devel@gnu.org
Subject: Re: ci.guix.info 504 gateway timeout (was Re: guix package builds, subsitutes and --no-build)
Date: Mon, 25 Feb 2019 15:46:43 -0500	[thread overview]
Message-ID: <20190225204643.GA19978@jasmine.lan> (raw)
In-Reply-To: <87pnrf1uff.fsf@elephly.net>

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

On Mon, Feb 25, 2019 at 09:31:48PM +0100, Ricardo Wurmus wrote:
> swedebugia <swedebugia@riseup.net> writes:
> > If this is not explained in the manual could you send a patch to include
> > this?
> 
> The service file already includes an “Environment” line.

Also, this 'Environment=' parameter is a feature of systemd services [0]
and applicable to any use of systemd. I don't think the Guix manual
needs to include specific examples of how to set environment variables
in third-party service managers.

[0] See the manual page systemd.service(5) or view it online:
https://www.freedesktop.org/software/systemd/man/systemd.service.html

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

  reply	other threads:[~2019-02-25 20:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87pnrm76ta.fsf@roquette.mug.biscuolo.net>
     [not found] ` <20190220214442.GA22965@jasmine.lan>
2019-02-21 15:14   ` ci.guix.info 504 gateway timeout (was Re: guix package builds, subsitutes and --no-build) Giovanni Biscuolo
2019-02-21 15:49     ` Ricardo Wurmus
2019-02-21 16:32       ` Mathieu Lirzin
2019-02-21 17:03         ` Giovanni Biscuolo
2019-02-21 18:29           ` Ricardo Wurmus
2019-02-22  4:46           ` Chris Marusich
2019-02-23 13:01         ` Alex Vong
2019-02-22  3:41     ` Chris Marusich
2019-02-25 13:11       ` Giovanni Biscuolo
2019-02-25 13:17         ` Ricardo Wurmus
2019-02-25 13:22           ` Ricardo Wurmus
2019-02-25 14:53             ` Giovanni Biscuolo
2019-02-25 15:10               ` Ricardo Wurmus
2019-02-25 15:37                 ` Mathieu Lirzin
2019-02-25 15:49                   ` Ricardo Wurmus
2019-02-25 16:18                     ` guix weather issue? " Giovanni Biscuolo
2019-02-26  7:07                       ` Chris Marusich
2019-02-26  9:33                         ` Giovanni Biscuolo
2019-02-27  7:29                           ` Chris Marusich
2019-02-27  8:21                             ` Giovanni Biscuolo
2019-02-27 17:53                               ` Chris Marusich
2019-02-27  8:26                             ` Björn Höfling
2019-03-03 16:06         ` ci.guix.info 504 gateway timeout " Mark H Weaver
2019-03-04 18:56           ` Leo Famulari
2019-02-25 19:13     ` swedebugia
2019-02-25 20:26       ` Giovanni Biscuolo
2019-02-25 20:31       ` Ricardo Wurmus
2019-02-25 20:46         ` Leo Famulari [this message]
2019-02-26 10:26           ` Giovanni Biscuolo

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=20190225204643.GA19978@jasmine.lan \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    /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).