Re: Corruption: empty refs/heads in otherwise filled repo: cannot clone?

From: Daniel Barkalow <barkalow@iabervon.org>
Date: Jun 30, 2008, 19:33 UTC
Message-ID: <alpine.LNX.1.00.0806301528500.19665@iabervon.org>
In-Reply-To: <200806301420.12872.J.Wielemaker@uva.nl>

On Mon, 30 Jun 2008, Jan Wielemaker wrote:

Show 17 quoted lines

> On Monday 30 June 2008 14:03, Jakub Narebski wrote:
> > Jan Wielemaker wrote:
> > > Summarising, I think the conclusion is that git pack-refs has somehow
> > > been run on this repository, and being a bare one this is not a
> > > particulary good idea right now. I have the impression I should `unpack'
> > > them by putting the appriate files in heads (done) and tags (now still)
> > > and (re)move packed-refs.
> >
> > If you use new enough git both on server and on clients it should
> > not have problems with packed-refs. I would rather check permissions
> > of $GIT_DIR and $GIT_DIR/packed-refs.
> 
> There is no permission problem, as a I proved by doing a recursive copy
> of the whole repo (cp -a, no errors) and the problem prevails on the
> copy. A serious scan for permission errors was my first step. Almost
> looks like something in the environment, but I can't find anything weird
> there either.

That's a "cp -a" as somebody else, I assume? (If it were as you or root, you'd generate a copy of the repository with any permission problem unchanged, since -a includes -p.)

	-Daniel
*This .sig left intentionally blank*