Wiki Tools

  • Find Page
  • Recent Changes
  • Page History
  • Attachments

Differences between revisions 91 and 254 (spanning 163 versions)
Revision 91 as of 2007-01-16 10:05:38
Size: 9834
Comment: note about pysqlite
Revision 254 as of 2013-05-24 18:21:05
Size: 344
Editor: jelmer
Comment: Just provide link to homepage, now restructuredtext support on the wiki is broken
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Introduction =
This plugin allows bzr direct access to Subversion repositories. This allows {{{bzr branch}}}, {{{bzr push}}}, {{{bzr pull}}}, and {{{bzr co}}} to work directly against Subversion repositories.
= Bazaar support for Subversion branches, working trees and repositories =
Line 5: Line 3:
The plugin can at the moment be used to commit to, pull from, merge from, push to and view logs of Subversion branches from Bazaar. bzr-svn is a plugin that allows Bazaar direct access to Subversion
repositories. It allows most bzr commands to work directly against Subversion
repositories, as if you were using bzr with a native bzr repository.
Line 7: Line 7:
It is fully functional, but has only been tested on a few different Subversion branches (samba, wireshark, subversion, cups), so should be considered alpha.

= Screenshots =
 * [ bzrk 1]
 * [ bzrk 2]
 * [ renames]
 * [ commits]
 * [ push]
 * [ push 2]
 * [ bzrk 3]
 * [ bzrk 4]

= Example branches =
All created by simply running {{{bzr branch ORIGINAL-URL}}}.

 * [ Samba 3] - Original at svn://
 * [ Samba 4] - Original at svn://
 * [ Samba docs] - Original at svn://
 * [ Subversion trunk] - Original at
 * [ Subversion 1.3.x] - Original at
 * [ Subversion 1.4.x] - Original at
 * [ Lorikeet trunk] - Original at svn://
 * [ Build Farm trunk] - Original at svn://
 * [ Samba4 Debian package] - Original at svn+ssh://
 * [ Samba3 Sid Debian package] - Original at svn+ssh://
 * [ Wireshark] - Original at
 * [ Samba pdbsql] - Original at
 * [ CUPS Trunk] - Original at
 * [ CUPS Kerberos] - Original at

More automatically imported branches can be found at .

If you are having problems checking out a particular branch, please file a bug report and include the branch URL (if the branch is public) and the backtrace.

= Features =
The following features are currently present:

 * Connecting to remote Subversion repositories over all protocols supported by Subversion itself (at present: svn://, svn+ssh://, http:// (webdav), file://) as well as dump files. Checkouts, lightweight checkouts and branching works.

 * Track Bazaar merges in Subversion. Merged revisions show up as ghosts.

 * Subversion working copies. Can be modified, queried ({{{bzr status}}} on a svn- native working copy created with {{{svn co}}} works) and committed from.

 * Committing to Subversion from Bazaar.

 * Push Bazaar revisions to Subversion. These revisions will show up in Subversion as a commit with the pushed revision as one of the parents.

 * Follow branch copies. Revision history is not truncated when a branch was copied in Subversion.

 * Efficiently uses network bandwidth.

 * Recognizes file metadata (executable bits, symlinks).

 * 'svn-import' command with functionality similar to ["svn2bzr"].

 * Ability to track merges done with SVK ( and write merges from SVK/Svn branches in a format understandable by SVK.

 * Generates consistent file ids and revision ids. Two branches made using this plugin of the same Subversion branch will result in *exactly* the same Bazaar branch.

 * Handles complex operations in Subversion: committing to two branches at once, upgrading directories to branches,
  . copies from early revisions, ...

= Future Enhancements =
In the future, I also hope to support:

== Features ==

 * Renames. Initial work has been done to support this, but the number of corner cases is wide, so support for this
  . has not been enabled by default yet. Those brave enough can test the current support out by registering SvnRenamingRepository instead of SvnRepository in

 * "True" push. This requires storing the Bazaar inventory and revision in Subversion revision properties.
  . Ideally, revision id aliases would have to be used so the revision id that is being 'overriden' can still exist. Once this is implemented, it would also be possible and make sense to store GPG signatures for commits in Subversion branches. This might require also storing 'bzr:inventory' and 'bzr:revision' properties in order to make sure the sha1's for a revision keep matching.

 * Proper Windows support. Most of the code depends on '/' being the path separator at the moment.

== Performance ==

Network-wise (both bandwidth and roundtrips), the plugin is in good shape. However, it is currently quite CPU-intensive for no good reason and I hope to make a couple of improvements in that area.
 * More efficient use of CPU

 * Override implementation of get_revision_delta(). Will speed up 'bzr log -v'

 * use svn_ra_replay() on systems that have Subversion 1.4. Saves a couple of roundtrips when fetching history. Initial work in branch at

 * implement svn_ra_get_dir_revs() in Subversion to fetch the properties set on a specific directory all at once.

 * Something in Subversion or the Python-Subversion bindings appears to be leaking a lot of memory.

== Properties ==
Some Subversion properties can currently not be represented in Bazaar and are therefore ignored for the time being:

 * 'svn:ignore' is not imported. There should be a `Repository.get_ignores(revid)' call in Bazaar rather than a magic '.bzrignore' file. Spec at

 * 'svn:externals'. Externals should be mapped to Bazaar 'by-reference' nested branches and the other way around. This can't be implemented until Bazaars nested branch support lands. AaronBentley's work in progress is at Has been delayed until after 0.9 because of required repository format changes.

 * 'svn:mime-type'

 * 'svn:eol-style'. Requires eol support in Bazaar.

 * 'svn:keywords'. Requires keywords support in Bazaar. Spec at

Other features currently held back by Bazaars feature set:

 * Horizon revision history. Most of the existing Subversion repositories are quite large and it would therefore be nice to be able to limit the amount of history that needs to be retrieved during checkouts. Subversion supports horizon history fine.
  . Spec at

 * Tracking copies.
  . Spec at

Features held back by Subversion:

 * Showing SVN merges as merges in Bazaar. This requires full merge information in Subversion, something which the Subversion folks are working on at the moment (see However, this seems to require support for cherry-picking. See

= Releases =
 * [ 0.3] (works with Bazaar 0.14 and higher)
 * [ 0.2] (works with Bazaar 0.13 and higher)
 * [ 0.1] (works with Bazaar 0.8 and higher)

= Requirements =

The plugin requires a couple of fixes to the Python bindings for Subversion that are only available in Subversion 1.5 (trunk). Debian/Ubuntu packages with these fixes backported are available in Ubuntu Edgy & Feisty and Debian Sid & Etch. You need the [ python-subversion] and [ libsvn0] packages.

A patch against Subversion 1.3.2 is also available at To build Subversions' Python bindings, run:

$ tar xvfj subversion-1.3.2.tar.bz2
$ cd subversion-1.3.2
$ ./ --release
$ ./configure
$ make
$ make check-swig-py
$ sudo make install install-swig-py

If you are using Python 2.4, you will need to have the pysqlite module installed. Python 2.5 and higher have sqlite support built in.

After ensuring these dependencies are met, you should be able to check out branches from Subversion using regular bzr commands.

= Bugs =
Please file bug reports in launchpad. The product URL for bzr-svn is

= Development =

== Branches ==

== Unit testing ==
Simply run 'bzr selftest svn'

Bazaar support for Subversion branches, working trees and repositories

bzr-svn is a plugin that allows Bazaar direct access to Subversion repositories. It allows most bzr commands to work directly against Subversion repositories, as if you were using bzr with a native bzr repository.