Command line commit fails

[spambouncer]

Hi list!

We're using a little script for our merging operations, which contains the 
following line for committing the results as a special merge user with a 
generated commit message:

svn ci --username foo --password bar  --no-auth-cache -F commit_msg.txt 
local\path 2> stderr.txt 

Upon this, a message box pops up with "SVN has stopped working. Debug/Close". 
However, committing still works when I use the TortoiseSVN GUI (Windows 
explorer extension). Any ideas?

This has stopped working with the most recent TortoiseSVN version 
(TortoiseSVN-1.7.10.23359-x64-svn-1.7.7). It used to work with previous 
versions, the last one I had was TortoiseSVN-1.7.7.22907-x64-svn-1.7.5.

My apologies if I posted to the wrong list because of using Tortoise, but it's 
the SVN command line which fails.

Best regards,
Spam Bouncer

svndumpfilter --skip-missing-merge-sources fails

[spambouncer]

Hi list!

I want to completely remove path/a from my repository using svndumpfilter 
exclude. Unfortunately, there's one revision where path/a/stuff is moved to 
path/b/stuff. As expected, svndumpfilter exits with an error message:

svndumpfilter: E23: Invalid copy source path '/path/a/stuff'

Now, there's this promising option --skip-missing-merge-sources, about which 
the manual says:

"Skips merge sources that have been removed as part of the filtering. Without 
this option, svndumpfilter will exit with an error if the merge source for a 
retained path is removed by filtering."

>From this text, I'm expecting svndumpfilter to successfully filter out path/a 
>and to not complain about the missing merge source when adding path/b/stuff. 
>Unfortunately, adding this option doesn't change the least bit. svndumpfilter 
>still displays the same error message at the same revision.

Here's my command line:

svndumpfilter --drop-empty-revs --renumber-revs --skip-missing-merge-sources 
exclude path/a/stuff < in.dump > out.dump

I also tried adding the options after the exclude part, doesn't make a 
difference. Also, you may have noted the leading slash in the error message. 
There's no leading slash in the dump file and adding it to the command line 
didn't help either.

Am I misinterpreting how --skip-missing-merge-sources is supposed to work? 
What's wrong? Is there a workaround so that I can keep path/b/stuff without 
keeping path/a?

Best regards and thanks for your help,
Spam Bouncer