[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: My observations and experience with cvs2svn.py on Windows

From: Tobias Ringström <tobias_at_ringstrom.mine.nu>
Date: 2004-02-17 21:58:23 CET

Bern McCarty wrote:

> I found RCS 5.7 binaries for the PC someplace and grabbed them because I
> didn't want to build it. The first problem that I encountered related to
> the way that cvs2svn.py uses the RCS 'co' command. co.exe was unable to
> locate the RCS file even though it was being given a fully qualified path to
> the file. After reading the RCS doc I could see why. Changing cvs2svn.py
> to add -x,v to the co.exe command-line seemed to fix the problem for me.

I've just commited error checking to cvs2svn.py when it runs external
command, which means that you will get an error message if that happens
in the future (instead of empty files).

> The other change I had to make to cvs2svn.py to get it to work on Windows
> involved binary files. I changed the access-mode string from 'r' to 'rb'
> where cvs2svn.py opens the pipe to read from the launched RCS co.exe
> process. Prior to making this change I got IOError exceptions when the pipe
> was closed on a co.exe that was extracting a binary file from RCS. These
> were the only two changes I had to make to get it to run to the end.

It is unfortunately not documented that you can use 'rb' for os.popen,
and indeed it fails on Linux. I wonder if 'rb' works reliably on all
Windows pythons.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 17 21:58:47 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.