This is apparently the situation at sf.net now. The solution is just to remove the project name from the host name.

Begin forwarded message:

From: Julian Rohrhuber rohrhuber@uni-hamburg.de Date: April 29, 2004 6:20:55 PM CDT To: SuperCollider developers list sc-dev@create.ucsb.edu Subject: Re: [sc-dev] sourceforge? Reply-To: SuperCollider developers list sc-dev@create.ucsb.edu

...

...

Yes I got that too before I wrecklessly removed the line in the ~/.ssh/known_hosts file. Now I can log into a server, but there is no repository there.

(2004-04-29 14:11:35 -Project CVS Service ) As of 2004-04-28 the CVS services will no longer function with the hostname of cvs.PROJECTNAME.sourceforge.net. You should change your CVS commands to use the host cvs.sourceforge.net and that should resolve any outstanding issues that you may have. This issue came about as a result of upgrading from BIND 8 to BIND 9 which doesn't allow for a wildcard in the middle of a hostname.

this means we have to change our CVSROOT var to a different value.

what is the equivalent of setenv in bash? last time I did this I think I had tshell, maybe, but this time it won't work.

so instead of

setenv CVSROOT :ext:username@cvs.supercollider.sourceforge.net:/cvsroot/supercollider

it should maybe be:

setenv CVSROOT :ext:username@cvs.sourceforge.net:/cvsroot/supercollider

or:

setenv CVSROOT :ext:username@cvs.sourceforge.net/supercollider:/cvsroot/supercollider

no idea.

. _______________________________________________ sc-dev mailing list sc-dev@create.ucsb.edu http://www.create.ucsb.edu/mailman/listinfo/sc-dev