threads / discuss / 43211

Re: error: Can't lock ref

Subject: Re: error: Can't lock ref

## tl;dr

3 messages between Dec 11, 2006 and Dec 11, 2006.

replies: 2people: 3as markdown or json

Jon Masters· Dec 11, 2006, 07:58 UTC · lore

error: Can't lock ref

Hi folks,

I've just pushed up a packed git repo:

http://www.kerneltools.org/pub/downloads/module-init-tools/devel/module-init-tools.git

Attempting to clone this repo using http generates the error in $subject. Brief searching via Google suggests this is an appache permissions problem - anyone got a trivially obvious apache config fix before I go trawling through to figure out what's up?

Andreas Ericsson· Dec 11, 2006, 09:08 UTC · re: Jon Masters · lore

Jon Masters wrote:

Show 12 quoted lines

> Hi folks,
> 
> I've just pushed up a packed git repo:
> 
> http://www.kerneltools.org/pub/downloads/module-init-tools/devel/module-init-tools.git 
> 
> 
> Attempting to clone this repo using http generates the error in 
> $subject. Brief searching via Google suggests this is an appache 
> permissions problem - anyone got a trivially obvious apache config fix 
> before I go trawling through to figure out what's up?
>

What does your apache error log say?

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se

Jon Masters· Dec 11, 2006, 16:35 UTC · re: Andreas Ericsson · lore

On Mon, 2006-12-11 at 10:08 +0100, Andreas Ericsson wrote:

Show 12 quoted lines

> Jon Masters wrote:
> > Hi folks,
> > 
> > I've just pushed up a packed git repo:
> > 
> > http://www.kerneltools.org/pub/downloads/module-init-tools/devel/module-init-tools.git 
> > 
> > 
> > Attempting to clone this repo using http generates the error in 
> > $subject. Brief searching via Google suggests this is an appache 
> > permissions problem - anyone got a trivially obvious apache config fix 
> > before I go trawling through to figure out what's up?

> What does your apache error log say?

That's just the thing - nothing. I get what looks like a good access in the access log, but then that error - I can play around, but I know others have discovered this to be some "known" apache problem. So, I'm hoping someone knows what that is, before I start debugging it.

Jon.