Re: Problem in step 9 of cvs2svn -- spaces in filenames?

On 02/16/2013 03:07 AM, Matt Ackeret wrote:
> I previously used cvs2svn a few years ago to convert another project and 
> had no troubles.  Now I'm converting another project, and it SEEMS to be
> related to spaces in filenames.  I searched the archives, and see various
> previous discussion that there is no problem and there are tests, so 
> what could be going wrong?
> 
> Disclaimer, we actually used 'wrapped cvs', but I have already used internally
> generated scripts to unwrap the CVS repository and that seems entirely
> unrelated.
> 
> I'm going to change some file names out of paranoia, but the info is otherwise
> exactly the same as what I'm seeing..
> 
> I'm running
> /Users/Shared/cvs2svn-2.4.0/cvs2svn --use-cvs --encoding=UTF-8 --dumpfile=cvs2svn-dump /tmp/PROJECT
> 
> and in step 9, pass 16 (I don't think that's too relevant since that just
> seems related to how many tags there are), it's failing with..
> 
> ...
> Starting Subversion r2197 / 4513
> ERROR: The command 'cvs -Q -R -f -d :local:/tmp/PROJECT co -r1.1 -p -kb Tests/TEST1/AAAA Verifier Help/AAAA Verifier Help idx' failed with exit status=1
> and the following output:
> cvs checkout: cannot chdir to /tmp/PROJECT/Tests/TEST1/AAAA: No such file or directory
> 
> The error seems entirely because it's not quoting the entire path that has
> spaces in it.

You can see exactly where this command is generated, in
cvs_revision_manager.py:CVSRevisionReader.get_pipe_command().  It is
definitely passing the filename as a single argument.

I suspect that the "cvs" executable that is in your path is a shell
script that calls the real cvs binary without proper quoting.

Michael

-- 
Michael Haggerty
[email protected]
http://softwareswirl.blogspot.com/

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=3048948

To unsubscribe from this discussion, e-mail: [[email protected]].