bzr-svn 0.3 - Other weird errors

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jelmer Vernooij wrote:
> Hi Nicholas,
> 
> This is an artefact caused by the fact that "true" pushes to Subversion
> aren't possible. Pushes are always "push-as-merged". Whenever you push a
> bazaar revision to Subversion, a new revision is added to Subversion
> that merges the revision you pushed. I'm afraid true pushes can't be
> supported easily. 
> 
> The example below works currently if you add a 'bzr pull' after the
> first 'bzr push'. That will fetch the new revision that was added to the
> Subversion mainline.
> 
> I'm open to suggestions for handling this better.

When you push a revision to svn from Bazaar, can't you just set a
property for the revision id?

Say you have 'x at y-123' as your revision id.  To 'push' to Subversion,
you commit a new revision.  svn sets its own changeset number, of
course, but you set the 'bzr-revision-id' property to 'x at y-123'

When bzr-svn is reading the contents of the repo later, it can look for
'bzr-revision-id' first, and fall back to the current revision-id
mechanism if that property isn't set.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFFsPBe0F+nu1YWqI0RArgyAJ4vPysYzreIglUPcT7Uco0Q9GBe2QCfdZp+
mZ9Fyh43fIv1ZnvjGeTudX0=
=LNpY
-----END PGP SIGNATURE-----