Hi,

% git clone http://git.openvz.org/pub/linux-2.6.24-openvz linux-2.6.24
Initialized empty Git repository in /usr/src/linux-2.6.24/.git/
Cannot get remote repository information.
Perhaps git-update-server-info needs to be run there?

This happens because the file
http://git.openvz.org/pub/linux-2.6.24-openvz/info/refs
is missing. It's not missing for any of the other repositories,
so it appears to be a genuine problem.

Please fix it. TIA.

-- 
     2. That which causes joy or happiness.

> git clone http://git.openvz.org/pub/linux-2.6.24-openvz linux-2.6.24
> Initialized empty Git repository in /usr/src/linux-2.6.24/.git/
> Cannot get remote repository information.
> Perhaps git-update-server-info needs to be run there?

> This happens because the file
> http://git.openvz.org/pub/linux-2.6.24-openvz/info/refs
> is missing. It's not missing for any of the other repositories,
> so it appears to be a genuine problem.
>
> Please fix it. TIA.

Can't you use native git protocol? That way you won't have to redownload
whole archive every time someone does git-repack on git.openvz.org

To switch to git protocol without redownloading change "http" to "git"
in .git/config -- it seems to work.

Josip Rodin wrote:
> Hi,
> 
> % git clone http://git.openvz.org/pub/linux-2.6.24-openvz linux-2.6.24
> Initialized empty Git repository in /usr/src/linux-2.6.24/.git/
> Cannot get remote repository information.
> Perhaps git-update-server-info needs to be run there?
> 
> This happens because the file
> http://git.openvz.org/pub/linux-2.6.24-openvz/info/refs
> is missing. It's not missing for any of the other repositories,
> so it appears to be a genuine problem.
> 
> Please fix it. TIA.
> 

Do not use http for cloning, it will suffer not only from
the refs file missing, but from anything it doesn't like. E.g.
tight beancounters limit (we hold git repo inside VE), slow
connection, etc. Use git protocol instead.

Thanks,
Pavel

On Mon, Feb 11, 2008 at 12:16:56PM +0300, Alexey Dobriyan wrote:
> > git clone http://git.openvz.org/pub/linux-2.6.24-openvz linux-2.6.24
> > Initialized empty Git repository in /usr/src/linux-2.6.24/.git/
> > Cannot get remote repository information.
> > Perhaps git-update-server-info needs to be run there?
> 
> > This happens because the file
> > http://git.openvz.org/pub/linux-2.6.24-openvz/info/refs
> > is missing. It's not missing for any of the other repositories,
> > so it appears to be a genuine problem.
> >
> > Please fix it. TIA.
> 
> Can't you use native git protocol? That way you won't have to redownload
> whole archive every time someone does git-repack on git.openvz.org
> 
> To switch to git protocol without redownloading change "http" to "git"
> in .git/config -- it seems to work.

Oh, I did use that later, but I still reported the lack of HTTP - because
I'd also like to use it in a place where it's a pain to let through another
protocol through the firewall (and 80/tcp is already there).

-- 
     2. That which causes joy or happiness.

On Mon, Feb 11, 2008 at 12:15:31PM +0100, Josip Rodin wrote:
> On Mon, Feb 11, 2008 at 12:16:56PM +0300, Alexey Dobriyan wrote:
> > > git clone http://git.openvz.org/pub/linux-2.6.24-openvz linux-2.6.24
> > > Initialized empty Git repository in /usr/src/linux-2.6.24/.git/
> > > Cannot get remote repository information.
> > > Perhaps git-update-server-info needs to be run there?
> > 
> > > This happens because the file
> > > http://git.openvz.org/pub/linux-2.6.24-openvz/info/refs
> > > is missing. It's not missing for any of the other repositories,
> > > so it appears to be a genuine problem.
> > >
> > > Please fix it. TIA.
> > 
> > Can't you use native git protocol? That way you won't have to redownload
> > whole archive every time someone does git-repack on git.openvz.org
> > 
> > To switch to git protocol without redownloading change "http" to "git"
> > in .git/config -- it seems to work.
> 
> Oh, I did use that later, but I still reported the lack of HTTP - because
> I'd also like to use it in a place where it's a pain to let through another
> protocol through the firewall (and 80/tcp is already there).

http should work fine now.