Re: vcp cvs issues

Looks like a bug, sorry.  Let me see what I can do to fix it.

Thanks,

Barrie



NIGGEMYER Brant wrote:

>I gave up trying to use sspi and just logged directly onto the CVS
>server and set my CVSROOT to the directory.  Which is fine by me because
>it is quite a bit faster. 
>
>I am having a problem passing a date parameter.
>
> D:\vcp>vcp cvs:Build/deploy/... -d ">=2004-11-18 5:26:30" -repo-id
>nm-cvs null:
>vcp: debugging enabled, see vcp.log
><vcp then proceeds to try to export the entire repository starting from
>day 1>
>
>
>
>I am not trying to turn on debugging; I am trying to set the date range.
>But it appears that it is taking the date range as the debug flag.
>vcp.exe 0.9 on win2k.  
>
>Thanks for the help!
>
>
>-----Original Message-----
>From: Barrie Slaymaker [mailto:[email protected]] 
>Sent: Wednesday, May 11, 2005 2:45 PM
>To: NIGGEMYER Brant
>Cc: [email protected]
>Subject: Re: [revml] vcp cvs issues
>
>Hmm, I wonder if it's a win32 vs. Unix case correctness issue.  Does the
>directory happen to be lower case ("build") somewhere, for instance in
>the CVS server's repository tree.
>
>- Barrie
>
>NIGGEMYER Brant wrote:
>
>  
>
>>In trying to migrate from cvs to perforce, vcp gives me the following
>>error:
>> 
>>unexpected stderr from 'cvs':
>>cvs: cvs [log aborted]: no such directory `Build'
>>cvs -Q -z9 -d:sspi:cltmi1dvrp:d:/cvsrepos/system log Build/deploy 
>>returned 1 not  0
>>stderr:
>>    cvs [log aborted]: no such directory `Build'
>> 
>>However, if I run this exact command from the command line:
>> 
>>cvs -Q -z9 -d:sspi:cltmi1dvrp:d:/cvsrepos/system log Build/deploy
>> 
>>it is successful. 
>> 
>>I am running vcp 0.9 on XP with CVSNT 2.5.01.
>> 
>>Any help is appreciated.
>> 
>> 
>>K. Brant Niggemyer
>>614-220-4422 (w)
>>614-571-4815 (m)
>> 
>>Confidentiality Statement:
>>
>>This message is intended only for the individual or entity to which it
>>    
>>
>
>  
>
>>is addressed. It may contain privileged, confidential information 
>>which is exempt from disclosure under applicable laws. If you are not 
>>the intended recipient, please note that you are strictly prohibited 
>>from disseminating or distributing this information (other than to the
>>    
>>
>
>  
>
>>intended recipient) or copying this information. If you have received 
>>this communication in error, please notify us immediately by return
>>    
>>
>email.
>  
>
>>-----------------------------------------------------------------------
>>-
>>
>>_______________________________________________
>>revml mailing list
>>[email protected]
>>http://maillist.perforce.com/mailman/listinfo/revml
>> 
>>
>>    
>>
>
>Confidentiality Statement:
>
>This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by return email.
>  
>