Re: [gitorious] problem cloning repo via https access

102 views
Skip to first unread message

Marius Mårnes Mathiesen

unread,
Oct 18, 2012, 4:21:15 AM10/18/12
to gito...@googlegroups.com
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.git seife
> > 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
Message has been deleted

schufti

unread,
Oct 18, 2012, 1:20:13 PM10/18/12
to gito...@googlegroups.com, zmall...@zmalltalker.com
Hi,
thank you for the quick answer that I forwarded to the repo owner.

Unfortunately it didn't change the situation. He reported that HAED points to MASTER and there are no branches in his repo.

Any other ideas what might be wrong or how to fix this?
Message has been deleted

schufti

unread,
Oct 24, 2012, 4:34:12 AM10/24/12
to gito...@googlegroups.com, zmall...@zmalltalker.com
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
Reply all
Reply to author
Forward
0 new messages