Hi Conrad,

I did use the syntax you suggested.  Below is the error.  Thanks.

~$ git clone /var/gitosis/repositories/vincentProject.git
Initialized empty Git repository in /home/master/vincentProject /.git/
fatal: failed to open /var/gitosis/repositories/vincentProject.git/

I think that’s because the repo belongs to the git user under
gitosis.  But I did add my SSH key to keydir folder and add myself to
the members list for this project.  I don’t know why git still
prevents me from cloning.  That’s why I had to use: git clone
g...@localhost:vincentProject.git clonedProject.  This works.  The only
drawback with this method is that it asks me for my passphrase for my
SSH key every time.


From: rubyonrails-t...@googlegroups.com [mailto:rubyonrails-
t...@googlegroups.com] On Behalf Of Conrad Taylor
Sent: Tuesday, January 19, 2010 8:15 PM
To: rubyonrails-t...@googlegroups.com
Subject: Re: [Rails] Re: git clone locally

On Tue, Jan 19, 2010 at 7:48 PM, Vincent P <ease...@gmail.com> wrote:
Hi Colin,

I get this error  if I just do git clone:  fatal: failed to open /var/

But the following works: git clone g...@localhost:vincentProject.git
That works after I add my public key to keydir folder under gitosis
and add my username to the members list for vincentProject in gitosis
config file.  This is fine.  But is there a better way?

One other problem: whenever I do a git pull, git asks me for my
passphrase for my key.  Is there anyway for me to avoid this?  I use
another account on a remote computer to do the pull and it works
without asking me for the passphrase of that account.


On Jan 19, 1:25 am, Colin Law <clan...@googlemail.com> wrote:
> 2010/1/19 Easebus <ease...@gmail.com>:
> > Thanks all.  I found out that I needed to use sudo before git in order for
> > the -local option to work in my case.
> You should not need to use --local or sudo, just
> git clone path/to/filename.git
> Colin

Vincent, you will need to use the following syntax instead:

`git clone path/to/directory_name`  # This is the same as `git clone -
l path/to/directory_name`.

For more information, I would recommend referencing the following web
sit for git related


Good luck,


On Jan 19, 1:55 pm, David Aguilar <dav...@gmail.com> wrote:
> On Tue, Jan 19, 2010 at 08:34:04AM -0800, Konstantin Khomoutov wrote:
> > On Jan 18, 2:42 am, Vincent P <ease...@gmail.com> wrote:
> > > I follow the instructions below to set up a git repository with
> > > gitosis on my home ubuntu server.  I can connect to the repository
> > > remotely perfectly and set up a new repository named My_Project.  I
> > > successfully push the content of My_Project to this repository using
> > > the remote computer with an SSH key.  Now I want to clone My_Project
> > > locally onto another directory within the unbuntu server.  How can I
> > > do this?  The instructions are only to clone remotely.  It appears
> > > that the clone command allows an "local" option but I haven't been
> > > able to get it to work.
> > git clone /path/to/the/repo
> > or
> > git clone file:///path/to/the/repo
> > The first will try to hardlink everything possible, the second will
> > not.
> > See `git help clone`.
> Since you already have gitosis running then you could also
> try cloning through the server.
> git clone g...@servername:My_Project.git
> If it says something along the lines of "permission denied" or
> something then it's likely that your $HOME/.ssh directory
> (and thus your ssh key) is different on your main box vs.
> on the server.  You can create a new key (just like you did
> for gitosis originally) and add it to your gitosis.conf
> if that is indeed the case.
> That'll help you avoid any permission/umask/etc. issues since
> it'll ensure that the 'git' user is the only one allowed to
> touch the repos.
> --
>                 David- Hide quoted text -
> - Show quoted text -
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to