Hi Jakub,
Thanks for the quick reply. Info:
On Monday 30 June 2008 12:10, Jakub Narebski wrote:
> Jan Wielemaker <J.Wielemaker@xxxxxx> writes:
> > I'm a bit puzzled. I have a bare repository, somehow without any files
> > in refs/heads.
>
> Do you have .git/packed-refs file? How do you have gc.packrefs set
Its a bare repo, so I'll forget the .git. Yes, I have that file and
it contains nice references, I checked a few by hand, and they have
the same SHA1 as the files I copied.
> ("git config --get gc.packrefs")? What are the git version on the
This gives no output, so I guess the answer is 'no'. Is that wrong?
This is indeed the case (config):
----------------------------------------------------------------
[core]
repositoryformatversion = 0
filemode = true
bare = true
sharedrepository = 1
[gitcvs]
enabled = 1
logfile = /home/git/pl.git/cvs.log
allbinary = 1
----------------------------------------------------------------
> clients that have trouble accessing repository, and what protocol
> (transport merhod) do they use: "file", http(s)/ftp, git, ssh?
I could reproduce the problem using the same git that maintains the bare
repository, which started as git-1.5.3.4 and is now 1.5.6.rc3. It
reproduces both using local file access and ssh. Other people have a
variety of versions. I know of concrete problems using the stable 1.5.5
over ssh.
The problem that I can't even clone is indeed after running a git-gc.
So, now I have all branch head refs double (in packed-refs and in
refs/heads). That explains ar least where they come from, but it fails
to explain why doing exactly the same using the same git on the same
repo as two users yields a different result. Of course, besides the
desire to understand how his works, I'm mostly interested in how to fix
this :-)
Thanks --- Jan
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
