Re: Trouble with cvs -d :pserver:[email protected]:/cvs -f -z3 update -PdA texi2html

Dumas Patrice <[email protected]> Wed, 12 Feb 2003 10:06:33 +0100
Newsgroups gmane.comp.tex.texi2html.devel
Message-ID <[email protected]>
> Oops.  Yep.  That's probably it.  I should have spotted it.  I'll get in 
> and rename it on the server.
> 
> Pat or anyone else who has the directory checked out may see errors on 
> their next update.  You can either grab a fresh checkout or just rm -rf 
> your Tests/cvs directory and rename the entry in Tests/CVS/Entries from 
> cvs to ccvs, or delete the entry entirely from the Entries file, and 
> then update.

I tried that removing the entry in Tests/CVS/Entries, and do a cvs up
in Tests. But the ccvs directory didn't appear. And then I made
$ cvs co .
But it was a very bad idea, now I have a lot of projects checked out
in the Tests directory (activitymail, *all public projects in domain,
autobuilder, cms2cvs, cmtools, cvsfororacleforms and a lot more)
:-(

I have checked out a fresh copy too. I think I will just release the old 
one (after commiting things that have to) if you think it is the right
thing to do.

> Someone will probably have to edit the Makefile.am with the new path 
> too.  I'll do it later if noone else has time.

I did it. One more thing remains to be done: change cvs_res directory
into ccvs_res. Derek, could you do that, please ?


Now I have some quite unrelated points, which relates more to the development
infrastructure and cvs. Maybe it isn't the right place to discuss about that ?

I think it might be nice to have an explanation of the cvs commands 
to do to connect to the cvs server once the tunnel is up. I used 

$ cvs -d :pserver:[email protected]:/cvs co texi2html

and things didn't went through the tunnel. Then I did (I believe this is right)

$ cvs -d :pserver:pertusus@localhost:/cvs login
$ cvs -d :pserver:pertusus@localhost:/cvs checkout texi2html

and things went through the tunnel. It is possible that I missed this 
information on the site.

Maybe it should also be mentionned that the tunnel won't work if the
client is allready a cvs server (that's a guess, I haven't tried, though).

And last the server could refuse some cvs commands if they are not issued
from localhost (commit, login...), and it would even be better if the server
refuse the connection before the password is send.

Pat