New svn client format (1.7+) breaks when checkout crosses filesystems

Howdy,

On my personal system, I got a new svn and as prompted by "your repo is
too old", upgraded it to the new format (svn 1.7.13).

And now I'm very hosed.

legolas:/var/local/scr# svn update
svn: E155037: Previous operation has not finished; run 'cleanup' if it was interrupted
legolas:/var/local/scr# svn cleanup
svn: E000018: Can't move '/.svn/tmp/svn-1FyLjO' to '/var/local/scr/btrfs-subvolume-backup': Invalid cross-device link

Indeed, I use svn across my entire system to keep track of changed files, and this
goes across filesystems. Been doing this for years, well until now I guess.

/ is my root
/var/local/scr is 2 levels of filesystems mounted on top
svn now keeps everything in /.svn it seems and naively assumes it can rename files across locations

I don't really want to rebuild my entire svn checkout in 7 different ones (one
per filesystem), not counting that I'd have to manually fix what svn state that
isn't synced on each of my client checkouts.

What are my options?
1) revert to svn 1.6 but I don't think I can revert my svn repo state
without going back to backups, I'm assuming it's a one way upgrade.

2) split my repo in 7 pieces, which sucks as explaine above (going to be hours of
manual work and checking over multiple systems) and reverting/rolling this out.

3) other :)

Thanks,
Marc

-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/