all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: pre-release [PATCH] git-service [v2]
Date: Fri, 26 Aug 2016 07:50:18 +0300	[thread overview]
Message-ID: <87fupsf81h.fsf@gmail.com> (raw)
In-Reply-To: <87r39dgold.fsf@we.make.ritual.n0.is> (ng0@we.make.ritual.n0.is's message of "Thu, 25 Aug 2016 09:55:10 +0000")

ng0 (2016-08-25 12:55 +0300) wrote:

> Hi,
>
> thanks for finding the errors. I applied your suggestions but the
> service still goes into respawn loop when the VM boots. Do you have any
> idea why this could happen?

Is there any output in syslog?  How does you patch look now?  What is
the exact "git daemon" command that is executing?  You can find this
command by looking at "/gnu/store/…-shepherd-git.scm" file: when you
built the system, guix told you that it would build this file.  If you
missed it, you can still find it by looking at
"/run/current-system/boot", there is a reference to
"/gnu/store/…-shepherd.conf", and there you can find a link to
"…-shepherd-git.scm" file.

-- 
Alex

  reply	other threads:[~2016-08-26  4:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 15:53 pre-release [PATCH] git-service ng0
2016-07-08 18:24 ` Thompson, David
2016-07-08 20:41   ` Ricardo Wurmus
2016-07-09  1:08     ` ng0
2016-07-13 10:23     ` ng0
2016-07-13 16:37     ` pre-release [PATCH] git-service [v2] ng0
2016-07-14  9:07       ` ng0
2016-08-11 15:55         ` ng0
2016-08-19  9:02           ` ng0
2016-08-22  8:03           ` Alex Kost
2016-08-25  9:55             ` ng0
2016-08-26  4:50               ` Alex Kost [this message]
2016-08-27 15:39                 ` ng0
2016-08-27 20:09                   ` Alex Kost
2016-08-27 20:44                     ` ng0
2016-08-28  0:04                       ` 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

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

  git send-email \
    --in-reply-to=87fupsf81h.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ng0@we.make.ritual.n0.is \
    /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.