[ 
https://issues.jenkins-ci.org/browse/JENKINS-13264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163134#comment-163134
 ] 

Valentin  Batz commented on JENKINS-13264:
------------------------------------------

I've experienced the same issue and traced it down to a cvsnt inconvenience.
I'll try to explain my findings.
The -d argument gets passed to the server. The server process creates a local 
copy in a tmp dir for the checkout with that argument as name. It does not 
create the required subdirectories and thats why the checkout will fail. I 
assume your cvsnt/cvs server is running in a unix environment, because works 
with backslashes because backslashes are valid in unix filenames/directories, 
and the first level directory is created in the tmpdir. 
I suggest not to pass the -d argument to the server, when doing 'partial 
checkouts' with subdirs.
I'd rather suggest to implement a client-side redirection of the 
files/directories.

                
> fail checkout 2 modules with different path
> -------------------------------------------
>
>                 Key: JENKINS-13264
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13264
>             Project: Jenkins
>          Issue Type: Bug
>          Components: cvs
>         Environment: linux
>            Reporter: Eric Co
>            Assignee: Michael Clarke
>             Fix For: current
>
>
> I create two cvs modules with the path
>   lib/flac-1.2.1
>   drv/linux/fuse
> when it check out, got the error:
>   cvs checkout -P -D 29 Mar 2012 11:40:15 +0800 -d lib/flac-1.2.1 
> lib/flac-1.2.1 
>   cvs [checkout aborted]: could not change directory to requested checkout 
> directory `lib': No such file or directory

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to