Comment 1 for bug 771397

I've tried several bzr releases (2.2.2 , 2.3.1, 2.4beta) which use different bzr-svn versions (1.0.4, 1.0.5, 1.1) on both my computers (osx and windows). The behavior is exactly the same :/ I've got my development environment also setup in a vmware machine (with bzr 2.2.2 + bzr-svn 1.0.4 installed), where I got some old version of the repo. I somehow managed to make bzr update on that virtual machine, but one of the files in fetched repository is terribly messed up (the version on svn server is perfectly fine). It looks like one of the commits, that were made into svn server by one of developers a couple of days ago, must be confusing bzr-svn and/or subvertpy, and leads to these problems (I'm the only person in the team using bzr-svn for repository access, so there is no one else, that could check this behavior). Please let me know, if you need more info/data to be able to fix this - I'd rather die than go back to "normal" svn client usage ;)
Thanks in advance!

cheers,
Bart ;)