git clone of linux-backports-modules-2.6.32 seems broken

Asked by Castor Fu

I tried cloning the lucid lbm git repository described by the ubuntu source package and got the following error with git version 1.7.0.4 on Ubuntu 10.4

% git clone http://kernel.ubuntu.com/git-repos/ubuntu/ubuntu-lucid-lbm.git
Initialized empty Git repository in /home/castor/bugs/backports/gitdir/ubuntu-lucid-lbm/.git/
fatal: http://kernel.ubuntu.com/git-repos/ubuntu/ubuntu-lucid-lbm.git/info/refs not found: did you run git update-server-info on the server?

If I look with a browser I don't see this file either. Is the repository supposed to be set up for general use?

Thanks,
Castor Fu

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu linux-backports-modules-2.6.32 Edit question
Assignee:
No assignee Edit question
Solved by:
Castor Fu
Solved:
Last query:
Last reply:
Revision history for this message
Simon Déziel (sdeziel) said :
#1

Hi Castor,

I was able to git clone using the git protocol instead of HTTP. The URL is different :

git clone git://kernel.ubuntu.com/ubuntu/ubuntu-lucid-lbm.git

See this for all details :
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid-lbm.git;a=summary

I hope this will help you.

Revision history for this message
Castor Fu (castor-alumni) said :
#2

Thanks! Should the Vcs-Git string in debian/control.stub.in be updated to put there?

Revision history for this message
Simon Déziel (sdeziel) said :
#3

I think you have found a bug so please fill a bug report to have it addressed.

simon@simon-laptop:~$ debcheckout linux-backports-modules-2.6.32
declared git repository at http://kernel.ubuntu.com/git-repos/ubuntu/ubuntu-lucid-lbm.git
git clone http://kernel.ubuntu.com/git-repos/ubuntu/ubuntu-lucid-lbm.git linux-backports-modules-2.6.32 ...
Initialized empty Git repository in /home/simon/linux-backports-modules-2.6.32/.git/
fatal: http://kernel.ubuntu.com/git-repos/ubuntu/ubuntu-lucid-lbm.git/info/refs not found: did you run git update-server-info on the server?
checkout failed (the command above returned a non-zero exit code)