bzr-svn version mismatch?

[Jelmer Vernooij]

Hi Thorsten,

On Mon, Jul 23, 2012 at 06:10:35PM +0200, Thorsten Glaser wrote:
> I fear I’ll still need to bug you.
> 
> After upgrading bzr from 2.1-something to 2.3.4, I cannot
> push to svn any more:
> 
> tglase at tglase:~/evolvis/tarent-5.1/src/www/pm $ bzr push
> Using saved push location: svn+ssh://mirabilos@evolvis.org/svnroot/evolvis/trunk/gforge_base/evolvisforge-5.1
> Upgrade to svn 1.5 or higher for faster retrieving of revision properties.
> bzr: ERROR: Please upgrade your Subversion client libraries to 1.5 or higher to be able to commit with Subversion mapping v4 (current version is (1, 6, 15, ''))
> 
> Yes, my svn is also a backport… and it worked with the
> previous versions of bzr:
> 
> /var/log/dpkg.log:2012-07-18 15:30:56 upgrade bzr 2.1.0-1~bazaar1~hardy1 2.3.4-0~bazaar1~hardy1
FWIW it's the version of bzr-svn that would be relevant here, rather
than the version of bzr itself.

You're probably getting this error because there are custom svn revision
properties in your repository. Older versions of svn can read these
just fine, but they don't support creating new revisions with revision
properties. bzr-svn refuses to use file properties for storing mapping
data after revision properties have been used in a repository (since
they're hard to mix, and file properties have a number of problems).

I would recommend upgrading your svn to at least svn 1.5, also because
there are a number of things have gotten faster and significantly
affect the performance of bzr-svn in 1.5.

Cheers,

Jelmer