Core dump with svn2git when using SVN 1.8

[Nicolás Alvarez]

Match rules are regular expressions, so if you need to match a
backslash you need to double it: \\

-- 
Nicolás

2017-08-06 15:31 GMT-03:00 John Lawlor <jk.lawlor at gmail.com>:
> Hi Nicolas,
>
> Thanks so much for your reply. The report has this line:
>
> fatal: Branch name doesn't conform to GIT standards:
> refs/tags/PM_2_2_Iteration2\CruiseControl
>
> I expect that it's the back slash instead of forward slash: '\' which is
> causing problems.
>
> I had a filter to skip that branch but it doesn't seem to be matching:
>
> match SharedModules/tags/PM_2_2_Iteration2/
> end match
>
> and if I try:
>
> match SharedModules/tags/PM_2_2_Iteration2\
> end match
>
> That gives me a malformed rule.
>
> Regards,
> John
>
>
>
> On 6 August 2017 at 19:11, Nicolás Alvarez <nicolas.alvarez at gmail.com>
> wrote:
>>
>>
>> El 6 ago 2017, a las 13:50, John Lawlor <jk.lawlor at gmail.com> escribió:
>>
>> Hi,
>>
>> I converted a SVN repository back in March using svn2git, and it ran fine.
>> As the live migration approaches I tried to run the conversion tool again
>> and I got a core dump a point in the SVN history that previously was fine.
>> When I ran the tool in March it didn't fail at this point:
>>
>> [...]
>> #2  0x00007ffdffe177b4 in qt_message_output
>> (msgType=msgType at entry=QtFatalMsg, buf=<optimized out>) at
>> global/qglobal.cpp:2323
>> #3  0x00007ffdffe17959 in qt_message(enum QtMsgType, const char *, typedef
>> __va_list_tag __va_list_tag *) (msgType=msgType at entry=QtFatalMsg,
>>     msg=msg at entry=0x438d38 "Failed to write to process: %s",
>> ap=ap at entry=0x7fff83b86d60) at global/qglobal.cpp:2369
>> #4  0x00007ffdffe18261 in qFatal (msg=msg at entry=0x438d38 "Failed to write
>> to process: %s") at global/qglobal.cpp:2552
>> #5  0x000000000042228d in QIODevice_write (baton=0x2ddc218,
>> data=<optimized out>, len=<optimized out>) at svn.cpp:237
>> [...]
>>
>> This branch was fine the last time I ran the conversion. I can't think
>> what the difference might be, it's the same machine that I ran it on in
>> March. The only difference I can think of is that I have using Subversion
>> 1.8. I can't be sure but I think that svn2git must have a dependency on
>> subversion-devel libraries, so if they are a different version that might be
>> the cause of the problem. I am not sure though. Any suggestions greatly
>> appreciated.
>>
>> Regards,
>> John
>>
>>
>> That looks like git-fast-import quit or crashed, and svn2git suddenly
>> finds it can't write to it and calls qFatal.
>>
>> See if there is any "fast import crash" file (I don't remember the exact
>> filename) inside the incomplete git repository.
>>
>> --
>> Nicolás
>
>