Problems converting a SVN repository

[Mads Kiilerich]

On 12/15/2014 02:28 PM, Andreas Tscharner wrote:
> Hello World,
>
> I tried to convert a SVN repository:
>
> C:\Users\ATs\Projects\src\tests\Mercurial>svn checkout 
> http://mscgen.googlecode.com/svn/trunk/ mscgen.svn
> A    mscgen.svn\test
> A    mscgen.svn\test\testinput10.msc
> A    mscgen.svn\test\testinput11.msc
> A    mscgen.svn\test\testinput20.msc
> A    mscgen.svn\test\testinput12.msc
> A    mscgen.svn\test\testinput21.msc
> A    mscgen.svn\test\testinput22.msc
> A    mscgen.svn\test\testinput13.msc
> A    mscgen.svn\test\testinput14.msc
> A    mscgen.svn\test\testinput15.msc
> ...
> ...
> ...
> A    mscgen.svn\examples\colour_sample.mscin
>  U   mscgen.svn
> Checked out revision 201.
>
> C:\Users\ATs\Projects\src\tests\Mercurial>hg --version
> Mercurial Distributed SCM (version 3.2.1)
> (siehe http://mercurial.selenic.com f³r mehr Information)
>
> Copyright (C) 2005-2014 Matt Mackall und andere
> Dies ist freie Software; siehe Quellen f³r Kopierbestimmungen. Es 
> besteht KEINE Gewõhrleistung f³r das Programm, nicht einmal der 
> Marktreife oder der Verwendbarkeit f³r einen bestimmten Zweck.
>
> C:\Users\ATs\Projects\src\tests\Mercurial>hg convert 
> http://mscgen.googlecode.com/svn/trunk/ mscgen.hg
> Initialisiere Ziel-Projektarchiv mscgen.hg
> Durchsuche Quelle...
> Sortiere...
> Konvertiere...
> 182 Initial directory structure.
> 181 First submission.
> 180 Added state description boxes into the entity lines.
> 179 Don't package .svn directories in source tarball.
> 178 Move box checking logic to after source and destination entities 
> have been validated.
> 177 Escape special characters in text strings for SVG output.
> 176 Remove auto-generated file when cleaning.
> 175 Correct getColourRef() such that it returns newly allocated colours.
> 174 Add -Wall -Wextra to makefiles.
> Transaktion abgebrochen!
> Zur├╝ckrollen abgeschlossen
> ** Unbekannter Fehler - bitte melden auf:
> ** http://mercurial.selenic.com/wiki/BugTracker
> ** Python 2.7.6 (default, Nov 10 2013, 19:24:24) [MSC v.1500 64 bit 
> (AMD64)]
> ** Mercurial Distributed SCM (Version 3.2.1)
> ** Erweiterungen geladen: shelve, strip, mq, rebase, patchbomb, convert
> Traceback (most recent call last):
>   File "hg", line 42, in <module>
>   File "mercurial\dispatch.pyo", line 28, in run
>   File "mercurial\dispatch.pyo", line 71, in dispatch
>   File "mercurial\dispatch.pyo", line 140, in _runcatch
>   File "mercurial\dispatch.pyo", line 850, in _dispatch
>   File "mercurial\dispatch.pyo", line 611, in runcommand
>   File "mercurial\dispatch.pyo", line 941, in _runcommand
>   File "mercurial\dispatch.pyo", line 912, in checkargs
>   File "mercurial\dispatch.pyo", line 847, in <lambda>
>   File "mercurial\util.pyo", line 677, in check
>   File "hgext\convert\__init__.pyo", line 338, in convert
>   File "hgext\convert\convcmd.pyo", line 533, in convert
>   File "hgext\convert\convcmd.pyo", line 450, in convert
>   File "hgext\convert\convcmd.pyo", line 418, in copy
>   File "hgext\convert\hg.pyo", line 205, in putcommit
>   File "mercurial\localrepo.pyo", line 63, in wrapper
>   File "mercurial\localrepo.pyo", line 1409, in commitctx
>   File "mercurial\context.pyo", line 61, in __getitem__
>   File "mercurial\context.pyo", line 1666, in filectx
>   File "hgext\convert\hg.pyo", line 139, in getfilectx
>   File "hgext\convert\convcmd.pyo", line 88, in getfile
>   File "hgext\convert\subversion.pyo", line 952, in getfile
>   File "libsvn\ra.pyo", line 599, in svn_ra_get_file
> svn.core.SubversionException: ("Server sent unexpected return value 
> (502 Bad Gateway) in response to
>  PROPFIND request for '/svn/!svn/vcc/default'", 175002)
>
> Is this a bug? Is it known? Or did I do something I should not do?

Converting to a different data model is always tricky - there might some 
invalid assumptions somewhere.

For a starter, I would start by trying using svnsync as described on 
http://mercurial.selenic.com/wiki/ConvertExtension#Converting_from_Subversion 
. It will either make it possible to debug it locally or tell us that it 
can't be reproduced locally.

> P.S. I had the same problem on my Debian Linux (unstable) when I tried 
> it last night...

Developers here will often have more experience with / trust in unix 
systems. Reporting it on linux will probably help getting the issue 
debugged / fixed.

/Mads