severity 399041 important thanks On Fri, Nov 17, 2006 at 12:29:05PM +0000, Gerrit Pape wrote: > On Fri, Nov 17, 2006 at 11:39:20AM +0100, Pierre Habouzit wrote: > > git ls-remote does not works like before (it seems it bails out when > > you give him $GIT_DIR as an argument) and breaks many commands, > > including gitk (but other fails also). > > > > this impedes git usability a *lot* as gitk is really a central tool to > > keep track of what's going on for quite complicated projects. > > > > instead of $GIT_DIR git ls-remote seems to want $GIT_DIR/.. wich is > > quite incompatible with an external .git as well anyway. > > Hi Pierre, I cannot reproduce this from your description. Also > git-ls-remote.sh didn't change since 1.4.3. Can you please paste the > exact command you run and the error message you receive?
Oh sorry, I forgot to do that.
I've repositories created with git-svn (maybe that's a reason, in fact
it seems it work with other repositories). and then when I run gitk --all, it
bails out and says:
$ gitk --all
Error in startup script: fatal: '.git': unable to chdir or not a git archive
fatal: unexpected EOF
Failed to find remote refs
while executing
"close $refd"
(procedure "readrefs" line 47)
invoked from within
"readrefs"
(file "/usr/bin/gitk" line 6281)
when I hack gitk around line 312 to make it do "git ls-remote [gitdir]/.."
it works as it's supposed to, hence me suposing that it was git ls-remote
fault. the fact that it works with other repos that are pure git ones show
that I'm actually wrong, so I've downgraded the severity accordingly (it only
renders the package unusable for /some/ uses of it :)).
Further checks shows taht in a "pure git" repository of mine I can do:
$ git ls-remote .git
b4bf40ddf386c8b0137c967448b60c104e624767 HEAD
b4bf40ddf386c8b0137c967448b60c104e624767 refs/heads/master
32b109474d5c1b57ab6a759cb15e9d27007546f1 refs/heads/origin
whereas in a git-svn one:
$ git ls-remote .git
fatal: '.git': unable to chdir or not a git archive
fatal: unexpected EOF
Failed to find remote refs
Sorry I did not checked a "pure" git repo first, I only did the git
ls-remote in a git-svn repo before. So I'm not really sure where the bug is
anymore, git-svn may be the good candidate after all :)
CHeers,
--
·O· Pierre Habouzit
··O [EMAIL PROTECTED]
OOO http://www.madism.org
pgpp3q9FX3uUz.pgp
Description: PGP signature
