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

From: Jan Wielemaker <wielemak@science.uva.nl>
Date: Oct 3, 2007, 18:42 UTC
Message-ID: <200710032042.14842.wielemak@science.uva.nl>
In-Reply-To: <Pine.LNX.4.64.0710031711070.28395@racer.site>

Dscho,

On Wednesday 03 October 2007 18:11, Johannes Schindelin wrote:

Show 8 quoted lines

> Hi,
>
> On Wed, 3 Oct 2007, Jan Wielemaker wrote:
> > 2007-10-03 12:25:16 : WARN - error 1 pserver cannot find the current
> > HEAD of module
>
> AFAIR we do not allow committing via pserver protocol.  Might that be your
> problem?

Thanks, but no. I'm using CVS over SSH. I've been looking around in git-cvsserver source a bit and it aborts quite quickly if you try a commit through pserver. I get a bit further, but it cannot find the HEAD revision for some reason and (from later message), if I try to checkout master instead of HEAD it finds the revision but I get a hash mismatch.

I've tried a bit debugging this, but in 15 years CVS experience I never really needed to debug the protocol and my GIT experience is only 2 weeks old :-(

My hope is I'm doing something fundamentally wrong and git-cvsserver just doesn't give a sensible error. I did setup the git repository using two different routes, one adviced in the CVS conversion manual. GIT operations work just fine, so does CVS checkout. I don't think you can to that much wrong with cvs over ssh clients, especially if checkout works just fine.

Does anyone out there has a working GIT <-> CVS+SHH setup? Based on what version of GIT? Using what route to create the repository?

	Thanks --- Jan