Re: KeyError in trunk

Michael Haggerty <[email protected]>
Newsgroups gmane.comp.version-control.subversion.cvs2svn.user
Message-ID <[email protected]>
Jamma Tino Schwarze wrote:
> On Tue, May 25, 2010 at 09:30:09AM +0200, Michael Haggerty wrote:
>> Jamma Tino Schwarze wrote:
>>> On Wed, May 19, 2010 at 03:55:47PM +0200, Michael Haggerty wrote:
>> If you turn on verbose logging ("-v") then cvs2svn should print out what
>> file it is processing.  The last file listed before the error should be
>> the culprit.
> 
> No, it's just doing it in pass 1, pass 4 just crashes without any
> indication of what file might be affacted. I just tried again with -v
> which didn't seem to change anything, output-wise.

When I run cvs2svn with the -v option, FilterSymbolsPass definitely
prints out the names of each RCS file before it processes it.  For
example, in trunk r5122, part of the output of the command "./cvs2svn -v
-s cvs2svn-tmp/main-svnrepos test-data/main-cvsrepos" is as follows:

----- pass 4 (FilterSymbolsPass) -----
Filtering out excluded symbols and summarizing items...
test-data/main-cvsrepos/full-prune/Attic/first,v
test-data/main-cvsrepos/full-prune/Attic/second,v
test-data/main-cvsrepos/full-prune-reappear/appears-later,v
test-data/main-cvsrepos/full-prune-reappear/sub/Attic/first,v
test-data/main-cvsrepos/full-prune-reappear/sub/Attic/second,v
[...]
Done

The output is generated by passes.py line 476, just a few lines before
one of the lines in your original stack trace.

Perhaps you are setting a different verbosity level (there are several)
in a config file?

Perhaps you are getting stdout and stderr mixed up?

Michael

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

To unsubscribe from this discussion, e-mail: [[email protected]].
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.