In article <[EMAIL PROTECTED]>, Manoj Srivastava <[EMAIL PROTECTED]> writes: > Hi, Eeek. I do not actually test the scripts for remote CVS > operation (and I haven't done so for months now), since I have a > local repository. Could you please do a bash -x /usr/bin/cvs-* > <whatever> and see if you can exactly where things are failing? A > script showing the errors would be nice.
Manoj, you're getting forgetful. This seems to be a cvs bug. See http://www.debian.org/Bugs/db/24/24585.html. IN case you're lazy, the output is below showing the bug. *sigh* I wish the cvs maintainer wasn't such a slacker. Maybe you could work around it. cvs-buildpackage has never worked for me, BTW, on client/server CVS. Manoj, I'd be happy to point you to my CVS area there and you could see for yourself. -- .....Adam Di [EMAIL PROTECTED]<URL:http://www.onShore.com/> <[EMAIL PROTECTED]:developers-reference> echo $CVSROOT :ext:[EMAIL PROTECTED]:/cvs/debian-doc <[EMAIL PROTECTED]:developers-reference> pwd /home/apharris/debian/developers-reference <[EMAIL PROTECTED]:developers-reference> ls CVS historic developers-reference typescript <[EMAIL PROTECTED]:developers-reference> cvs -q export -d /home/apharris/debian/developers-reference/developers-reference-2.4.1.3 -r debian_version_2_4_1_3 developers-reference cvs [export aborted]: cannot make directory : No such file or directory <[EMAIL PROTECTED]:developers-reference> cvs -q export -d developers-reference-2.4.1.3 -r debian_version_2_4_1_3 developers-reference U developers-reference-2.4.1.3/developers-reference.desc U developers-reference-2.4.1.3/developers-reference.sgml
