hi, I have tried now random repos and didn't find one where it's working ....
So either it is not working from beginning or the error hits all repos sooner or later. what is funny, ist that pulls work fine after an initial clone via git: It is enough to copy .git directory and change the url in config to https.... After this a git reset --hard does the trick ... maybe it is worth to look into this or just have a note that http clone is not working as intended to spare others frustration thanks On Thursday, October 18, 2012 10:21:20 AM UTC+2, Marius Mårnes Mathiesen wrote: > > On Thu, Oct 18, 2012 at 12:45:08AM -0700, schufti wrote: > > Hi, > > some time in the past I must have been able to clone repos via https > since > > my dev. machine is behind a natting firewall-proxy allowing http(s) > access > > only. And up to now I didn't experience any problem pulling from these > > repos. But recently I had to clone a repo to a new machine and suddenly > I > > was presented with the following message: > > > > git clone https://git.gitorious.org/neutrino-hd/buildsystem-cs.gitseife > > > Cloning into 'seife'... > > > warning: remote HEAD refers to nonexistent ref, unable to checkout. > > The issue here is that our Git-over-HTTP service uses the "dumb" HTTP > protocol; which pulls down commits one by one. The first thing that > this service does is to try to locate the HEAD of the repository; > which should point to a valid ref (branch). It looks like the HEAD > reference on this repository points to a non-existing ref. > > The owner of the repository should be able to change which branch HEAD > points to in the repository using the Gitorious UI. > > > -- > > Cheers, > - Marius > -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected]
