[cvsnt] Repeat issue: Export doesnt workproperlyanymore(2.0.4and 2.0.8)

[Bo Berglund]

OK, I can reproduce this as well. I have uninstalled CVSNT from my laptop
(I will not use the server for these tests). Then reinstalled 2.0.8 and
verified proper functioning.
I have a repository in C:\cvsrepo\test which is served by the server using
repository prefix as /test.
Here I have a module AdamTest with a subdir Doc contianing some files.
What I have done is described in the following copied from a command
window in a new empty folder c:\tmp\cvstst :

C:\tmp\cvstst>set CVSROOT=:local:c:/cvsrepo/test

C:\tmp\cvstst>cvs export -r HEAD -d EXP -N AdamTest/Doc
cvs export: Updating EXP/AdamTest/Doc
U EXP/AdamTest/Doc/Test file with spaces.txt
U EXP/AdamTest/Doc/readme.txt

C:\tmp\cvstst>set CVSROOT=:sspi:welebobe:/TEST

C:\tmp\cvstst>cvs export -r HEAD -d EXP2 -N AdamTest/Doc
cvs export: Updating EXP2
U EXP2/Test file with spaces.txt
U EXP2/readme.txt

C:\tmp\cvstst>set CVSROOT=""

C:\tmp\cvstst>cvs -d :sspi:welebobe:/test export -r HEAD -d EXP3 -N AdamTest/Doc
cvs export: Updating EXP3
U EXP3/Test file with spaces.txt
U EXP3/readme.txt

C:\tmp\cvstst>cvs -d c:/cvsrepo/test export -r HEAD -d EXP4 -N AdamTest/Doc
cvs export: Updating EXP4/AdamTest/Doc
U EXP4/AdamTest/Doc/Test file with spaces.txt
U EXP4/AdamTest/Doc/readme.txt

Note that when I set the protocol to :local: and specify the full path to the
repository the export command works one way and if I use :sspi: it works the
other way. Also using the cvs -d command line parameter works the same way.
The complete dialogue including the setting of the CVSROOT environment
variable is shown above, there is nothing else I had to do except this.

/Bo

-----Original Message-----
From: Tony Hoyle [mailto:tmh at nodomain.org]
Sent: den 13 augusti 2003 12:40
To: cvsnt at cvsnt.org
Subject: Re: [cvsnt] Repeat issue: Export doesnt
workproperlyanymore(2.0.4and 2.0.8)


On Tue, 12 Aug 2003 23:25:10 -0700, "Glen Starrett" <grstarrett at cox.net>
wrote:

>A-HA!!!!!!!!!!  I figured out WHY it works for Tony and yet I can
>reproduce Bo's problem myself.  Note Tony's command vs. mine and Bo's:
>
>Tony:	cvs -d d:/repo export -r HEAD -d foo -N develop/include cvs 
>Me:	cvs -d :pserver:gstarret at stanley:/home/cvsroot export -r HEAD -d
>useme2 -N cool/images 
>Bo:	cvs export -r HEAD -d WSMDB-CS -N Drivers/sentinel
>
>Tony is using local protocol, vs. pserver for me and ??? For Bo.  I ran
>this on my cvsnt 2.0.8 Linux server as verification:

Nope... not that, unfortunately:

D:\t>cvs -d :pserver:tmh at localhost:d:/repo export -r HEAD -d foo -N
develop/include
cvs export: Updating foo/develop/include
U foo/develop/include/16BitHeaders.h
U foo/develop/include/AFXIMPL.H
U foo/develop/include/DbgHelp.h
...

Or even...

tmh at betty:~$ cvs -d :pserver:tmh at cvs.cvsnt.org:/usr/local/cvs export -r HEAD
-d foo -N cvsnt/windows-NT

cvs export: Updating foo/cvsnt/windows-NT
U foo/cvsnt/windows-NT/.cvsignore
U foo/cvsnt/windows-NT/ChangeLog
U foo/cvsnt/windows-NT/Makefile.am
U foo/cvsnt/windows-NT/Makefile.in
U foo/cvsnt/windows-NT/README
...

Tony

_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt