Re: cvs with different versions

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Marques <address@hidden> writes:

> I'm experiencing problems with CVS dying unexpectivly using ssh as an 
> external autenticationmethod, and all I did was upgrade the version on 
> my server (debian testing) to version:
> 
> $ cvs -v
> 
> Concurrent Versions System (CVS) 1.12.13 (client/server)
> 
> On my client (workstation machine) I have fedora:
> 
> $ cvs -v
> 
> Concurrent Versions System (CVS) 1.11.17 (client/server)
> 
> And I keep getting these errors when trying to update from my WS
> on my server:
> 
> Terminated with fatal signal 10
> 
> This doesn't happen when doing updates locally on the server.
> 
> Could it be a problem with the fact that I have different version of
> CVS working in the 2 machines?

I have been using a mixture of CVS 1.11.x clients with CVS 1.12.x
servers for a long time now with no problems.

Do all cvs commands terminate with the fatal signal?

What does the 'cvs version' command give you?

If you do tracing with 'cvs -t ...your-command-options-here...' what
extra tracing to you see?

        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (FreeBSD)

iD8DBQFFfutECg7APGsDnFERAo6TAJ0bCwaTP6K0o0pHH0+UOP8+Sx3NEwCff//e
lOKY107xfKRynkfiq5hc5gk=
=JigP
-----END PGP SIGNATURE-----