Migration SVN to Bitbucket, Subversion Author Mapping File

[Roy Peulen]

Hi,

I'm migrating our current SVN repositories to Bitbucket follwing the guideline:

https://go-dvcs.atlassian.com/display/aod/Migrating+from+Subversion+to+Mercurial

The problem is i'm stucked on creating the Author Mapping File using the provided migration-script, i'm receiving the folowwing error:

javax.xml.stream.XMLStreamException: ParseError at [row,col]:[3,1]
Message: XML document structures must start and end within the same entity.
at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(Unknown Source)
at scales.xml.XmlPull$class.pumpEvent(PullIterator.scala:167)
at scales.xml.XmlPulls$$anon$1.pumpEvent(XmlPull.scala:118)
at scales.xml.XmlPull$class.next(PullIterator.scala:149)
at scales.xml.XmlPulls$$anon$1.next(XmlPull.scala:118)
at scales.xml.XmlPulls$$anon$1.next(XmlPull.scala:118)
at scales.utils.IterateeImplicits$$anon$2.apply(Iteratees.scala:35)
at scales.utils.IterateeImplicits$$anon$2.apply(Iteratees.scala:29)
at scalaz.IterV$class.apply(Iteratee.scala:14)
at scalaz.IterV$Cont$$anon$2.apply(Iteratee.scala:55)
at scales.utils.Iteratees$ResumableIterIterator.<init>(Iteratees.scala:198)
at scales.utils.Iteratees$class.withIter(Iteratees.scala:216)
at scales.utils.package$.withIter(package.scala:3)
at scales.xml.PullIteratees$Iterate.<init>(PullIteratees.scala:178)
at scales.xml.PullIteratees$class.iterate(PullIteratees.scala:202)
at scales.xml.package$.iterate(package.scala:3)
at scales.xml.PullIteratees$class.iterate(PullIteratees.scala:172)
at scales.xml.package$.iterate(package.scala:3)
at com.atlassian.svn2git.Authors$.parseUserXml(Authors.scala:151)
at com.atlassian.svn2git.Authors$$anonfun$5.apply(Authors.scala:137)
at com.atlassian.svn2git.Authors$$anonfun$5.apply(Authors.scala:136)
at scala.sys.process.ProcessBuilderImpl$Simple$$anonfun$3.apply$mcV$sp(ProcessBuilderImpl.scala:73)
at scala.sys.process.ProcessImpl$Spawn$$anon$1.run(ProcessImpl.scala:22)

Does somebody have a solution for this?

Thanx in advance

Greetings,

Roy

[AgentSmith · Accepted solution]

On the surface it looks like its complaining about malformed data. Look into the "svn status" command and search for malformed lines that begin with ~ or ! for example. If you find them, remove them and try it again.

Hope this helps!