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

On 02/18/2013 08:04 PM, Matt Ackeret wrote:
> On Fri, 15 Feb 2013, Michael Haggerty wrote:
>> 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.
> 
> Thanks, I'll look at that..  but at the very least, /usr/bin/cvs is really a
> binary (more-ing it is not good!).

Other ideas:

* Use --cvs=PATH to be sure that cvs2svn is invoking the cvs command
that you want.

* Use --use-internal-co to retrieve the revisions using internal code
(avoids the need for the cvs command entirely).

But please try to figure out the source of the problem anyway to help
the community.  If there is a bug, we want to know about it and fix it.

> Another question I have about cvs in general -- could I theoretically just
> remove this entire directory from my local copy of the repository to work
> around the issue?  If someone really needed the repository history of this
> tool, they could get it from the real cvs repository.  (That tool was already
> moved somewhere else long ago, and I don't think the history of it is too
> important.)

Sure you could do it.  But there is no need to.  cvs2svn can handle
spaces in filenames just fine.  If you can't get it to work, please file
a bug.  The FAQ [1] gives detailed instructions for filing a useful bug
report, including an automated procedure for stripping secret
information from your repository if necessary and for shrinking the size
of the test repo, usually to one or two files.

Michael

[1] http://cvs2svn.tigris.org/faq.html#reportingbugs

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

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

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