All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Kestenholz <mk@spinlock.ch>
To: Erez Zilber <erezzi.list@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-clone works with ssh but not with http/https/git
Date: Tue, 24 Jun 2008 13:21:57 +0200	[thread overview]
Message-ID: <1214306517.6441.10.camel@localhost> (raw)
In-Reply-To: <ce513bcc0806240415h669d1725uf7b6e495995ab459@mail.gmail.com>

On Tue, 2008-06-24 at 14:15 +0300, Erez Zilber wrote:
> Hi,
> 
> I'm able to git-clone a tree using ssh:
> 
> [root@kd001 t]# git-clone
> ssh://erez.zilber@kites/pub/git/erez.zilber/my_test.git
> Initialized empty Git repository in /home/erez.zilber/work/tmp/t/my_test/.git/
> erez.zilber@kites's password:
> remote: Counting objects: 9, done.
> remote: Compressing objects: 100% (5/5), done.
> remote: Total 9 (delta 0), reused 0 (delta 0)
> Receiving objects: 100% (9/9), done.
> 
> However, it doesn't work with http/https/git:
> 
> [root@kd001 t]# git-clone http://kites/pub/git/erez.zilber/my_test.git
> Initialized empty Git repository in /home/erez.zilber/work/tmp/t/my_test/.git/
> Cannot get remote repository information.
> Perhaps git-update-server-info needs to be run there?
> 

Maybe you should run git-update-server-info in the repository on the
server?

> [root@kd001 t]# git-clone https://kites/pub/git/erez.zilber/my_test.git
> Initialized empty Git repository in /home/erez.zilber/work/tmp/t/my_test/.git/
> Cannot get remote repository information.
> Perhaps git-update-server-info needs to be run there?


Maybe you should run git-update-server-info in the repository on the
server?

By the way, try enabling the post-update hook -- it runs
update-server-info for you automatically after pushing to your server
(make the script $GIT_DIR/hooks/post-update executable)

> [root@kd001 t]# git-clone git://kites/pub/git/erez.zilber/my_test.git
> Initialized empty Git repository in /home/erez.zilber/work/tmp/t/my_test/.git/
> kites[0: 172.16.1.11]: errno=Connection refused
> fatal: unable to connect a socket (Connection refused)
> fetch-pack from 'git://kites/pub/git/erez.zilber/my_test.git' failed.
> 

Is the git daemon running on your server? You need to configure inetd or
git-daemon yourself, that is not done automatically for you.


-- 
http://spinlock.ch/blog/

  reply	other threads:[~2008-06-24 11:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 11:15 git-clone works with ssh but not with http/https/git Erez Zilber
2008-06-24 11:21 ` Matthias Kestenholz [this message]
2008-06-24 11:45   ` Erez Zilber
2008-06-24 11:48     ` Johannes Schindelin
2008-06-24 12:07       ` Erez Zilber
2008-06-24 12:25         ` Jakub Narebski
2008-06-24 13:42           ` Erez Zilber
2008-06-24 13:54             ` Anton Gladkov
2008-06-24 13:59               ` Anton Gladkov
2008-06-24 14:02                 ` Matthias Kestenholz
2008-06-24 14:16               ` Erez Zilber
2008-06-24 18:58               ` Jakub Narebski
2008-06-24 14:05             ` Matthieu Moy
2008-06-24 12:41         ` Johannes Sixt
2008-06-24 12:35     ` Robert Haines
2008-06-24 13:53       ` Erez Zilber
2008-06-24 14:08         ` Robert Haines
2008-06-24 14:45           ` Erez Zilber
2008-06-24 17:10             ` Daniel Barkalow
2008-06-25  6:56               ` Erez Zilber

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=1214306517.6441.10.camel@localhost \
    --to=mk@spinlock.ch \
    --cc=erezzi.list@gmail.com \
    --cc=git@vger.kernel.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.
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.