Hi Nico,
So receive-pack should be enabled,
Sadly, I know very little about git and can't debug it on either the sv
side or the client side. All I can report is that a whole lot of
projects have enabled git without any problem, which is not helpful ...
Since the sv people most likely to look at this are not
savannah-register-public (which is only supposed to get automail
anyway), I'm cc-ing this to savannah-hackers.
John/Bob/Michael/whomever, please see full msg below. This is about
Nico's new blogcomment project, which I enabled yesterday.
Best,
Karl
Date: Tue, 06 Aug 2013 11:52:55 -0400
From: Nico Cesar <n...@fsf.org>
CC: Karl Berry <k...@gnu.org>, savannah-register-pub...@gnu.org
Subject: Re: [task #12752] Submission of Blog Comment
karl> Hi Nico. Looks good to me. I approved the project, the cron jobs
> should do their stuff within the hour.
>
> I believe CVS is enabled by default, there's currently no way around that (and
> no way to use anything else for the project web pages, if you plan to have
> any). You can enable git under "select features", as you probably know.
I just enabled it, waited for the crons to create it and I get the
following error:
$ git commit -m "starting the project "
[master (root-commit) c8deff0] starting the project
3 files changed, 1007 insertions(+)
create mode 100644 LICENSE
create mode 100755 disqus
create mode 100755 guardian.py
$ git push
fatal: The remote end hung up unexpectedly
Because I have root on that machine (advantages of being a FSF sysadmin)
I see on /var/log/syslog:
Aug 6 15:50:32 vcs git-daemon[30758]: 'receive-pack': service not
enabled for '/srv/git/blogcomment.git'
So receive-pack should be enabled,
How do you usually handle this?
Am I doing something wrong?
Thanks,
Nico
