Re: git-cvsserver commit trouble (unexpected end of file in client)

From: Jan Wielemaker <wielemak@science.uva.nl>
Date: Oct 3, 2007, 14:57 UTC
Message-ID: <200710031657.08622.wielemak@science.uva.nl>
In-Reply-To: <200710031513.44446.wielemak@science.uva.nl>

On Wednesday 03 October 2007 15:13, Jan Wielemaker wrote:

Show 10 quoted lines

> $ mkdir /pub/my-repo.git
> $ cd /pub/my-repo.git
> $ git --bare init --shared
> $ git --bare fetch /home/alice/myproject master:master
>
> Checked out freshly using CVS. No problem. But committing a change,
> nothing changed :-( The log output is exactly the same, showing only
> refs/heads/master. I'm starting to suspect git-cvsserver afterall, but
> the docs suggests it is operational for quite a while. Could someone
> give me a clue on what am I missed?

More tests ... As it didn't like the HEAD, and insisted it only knows about master, I though what happens on

	cvs -d :ext:user@host:/git-repos.git co master

<works fine>
<edit>
	cvs commit
Commit failed (unknown reason)

:-(  Logfile says:

================================================================ 2007-10-03 16:43:37 : INFO - req_ci : [NULL] 2007-10-03 16:43:37 : INFO - Lockless commit start, basing commit on '/tmp/VP2P VNHPs0/6t4xncbMoN', index file is '/tmp/VP2PVNHPs0/SO4A6pzpau' 2007-10-03 16:43:37 : INFO - Start git show-ref -s refs/heads/master 2007-10-03 16:43:37 : INFO - Heads: 0b7b372d525a4fe7f662996fec9cd11b1038a6be re fs/heads/master

2007-10-03 16:43:37 : INFO - parenthash = 0b7b372d525a4fe7f662996fec9cd11b1038a 6be

2007-10-03 16:43:37 : INFO - Created index '/tmp/VP2PVNHPs0/SO4A6pzpau' with fo r head master - exit status 0 2007-10-03 16:43:37 : INFO - Committing collections-representation.txt 2007-10-03 16:43:37 : DEBUG - rename /tmp/VP2PVNHPs0/0SfbkMq6AN collections-repr esentation.txt 2007-10-03 16:43:37 : DEBUG - chmod u+rw-x collections-representation.txt 2007-10-03 16:43:37 : INFO - Updating file 'collections-representation.txt' 2007-10-03 16:43:37 : DEBUG - Treehash : aba0f583177b3b7fca05935452de22612164a7f 3, Parenthash : 0b7b372d525a4fe7f662996fec9cd11b1038a6be 2007-10-03 16:43:37 : INFO - Commit hash : 2007-10-03 16:43:37 : WARN - Commit failed (Invalid commit hash) ================================================================

!? What happens? Is git-cvsserver completely broken and should I thus forget about GIT for now (saying we cannot deal with cvs commit is politically unacceptable in this project)? Any clue?

	Please help

		--- Jan