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

RE: Rcsparse.py

From: Dale Hirt <dale_at_sbcltd.com>
Date: 2003-02-25 23:58:34 CET

Karl,

I tried this with a sourceforge project that I am currently owner of,
libzvtmm. Went to http://cvs.sourceforge.net/cvstarballs/ and picked up
libzvtmm-cvsroot.tar.gz. I un{gzip, tar} in an empty directory, getting a
folder of libzvtmm. Then, I run the following command:

python cvs2svn.py --create -s svn-libzvtmm libzvtmm

I've attached the single binary ,v file that it chokes on. I am also on
windows, though. I don't know if that will make a difference.

Thanks,

Dale

-----Original Message-----
From: Karl Fogel [mailto:kfogel@newton.ch.collab.net]
Sent: Tuesday, February 25, 2003 2:16 PM
To: Dale Hirt
Cc: Subversion Development Mailing List (E-mail)
Subject: Re: Rcsparse.py

Dale Hirt <dale@sbcltd.com> writes:
> I finally manage to get everything compiled and working, and what happens?
> Rcsparse.py chokes on the first binary cvs file it finds. Ugh. Any
ideas?
> The stack trace follows for your fun and amusement.

Even more useful than a stack trace: what was the command you ran, and
the dataset you ran it?on. If you could create an issue with that
attached (or just attach the minimal data needed to reproduce the
problem), that would be very helpful.

I tried to reproduce this with a ,v file whose revision 1.1 contained
a stretch of binary data (taken from /bin/ls), and did not see the
errors you saw. cvs2svn.py made it through all 4 passes.

If you can supply a repro recipe, I will jump on this... :-) (hint hint)

Thanks,
-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Received on Wed Feb 26 00:20:02 2003

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

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