Grant Rettke wrote:
> Jelmer wrote: "Was the branch itself renamed or its parent (stx-object-
> getdef) ?"
>
> The branch itself.
>
> Jelmer wrote: "Can you perhaps just paste the output of "svn log -v
> -r1190" ?"
Unfortunately I still can't reproduce this. I'm suspecting the fact that
you're on Windows may be related here.
Please run "bzr selftest bzrlib.plugins.svn" and attach the output here.
The errors from that should hopefully allow us to fix this problem if it
is indeed Windows-specific.
If you have access to a Linux or Mac OS X machine, is there any chance
you can try the svn-import run on that, to confirm this is a Windows
specific issue?
Cheers,
Jelmer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Grant Rettke wrote:
> Jelmer wrote: "Was the branch itself renamed or its parent (stx-object-
> getdef) ?"
>
> The branch itself.
>
> Jelmer wrote: "Can you perhaps just paste the output of "svn log -v
> -r1190" ?"
Unfortunately I still can't reproduce this. I'm suspecting the fact that
you're on Windows may be related here.
Please run "bzr selftest bzrlib.plugins.svn" and attach the output here.
The errors from that should hopefully allow us to fix this problem if it
is indeed Windows-specific.
If you have access to a Linux or Mac OS X machine, is there any chance
you can try the svn-import run on that, to confirm this is a Windows
specific issue?
Cheers,
Jelmer enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iJwEAQECAAYFAkm h/sgACgkQDLQl4Q YPZuWY0QQAndBEO tHGjOsdWUaEhdaG WMEL ULdZTxQYXA64yXi oIqu6cLzluyN6Ae MOyZ619ZtcLIZsw pUY9WIR/ C30p PhPh4kpF+ KzqDzofCn3IDio4 J/0/x3ZgV0enQkT XehNNHyF1RDshRs b 85+1RlXgtM=
WT4yeq+
vO7WSGP8/
BIyqRFre+
=uKte
-----END PGP SIGNATURE-----