The migration was rather easy
sudo aptitude install bzr-svn # patch (see below) bzr branch svn://svn.debian.org/reportbug-ng # That's right I branch directly from a SVN repo! # ignore the error bzr push --use-existing-dir sftp://email@example.com/bzr/reportbug-ng
To get your own branch:
bzr branch http://bzr.debian.org/bzr/reportbug-ng/
Bzr-svn really makes it easy to migrate from svn to bzr... well, in theory. In practice we have #415721, but fortunately there is an easy workaround. Just temporarily apply this trivial patch:
--- /usr/share/pycentral/bzr-svn/site-packages/bzrlib/plugins/svn/__init__.py 2007-04-20 09:30:00.000000000 +0200 +++ /usr/share/pycentral/bzr-svn/site-packages/bzrlib/plugins/svn/__init__.py.new 2007-04-20 09:30:24.000000000 +0200 @@ -23,7 +23,7 @@ import bzrlib
__version__ = '0.2.0'
-required_bzr_version = (0,13)
+#required_bzr_version = (0,13)
"""Check that bzrlib is compatible.
and life is good again.
The reason why I switched from a centralized to a distributed RCS was that I really like the option to do (small) local checkins and just do the "real" checkin when the work is done. In terms of BZR it means commits to my local branch for smaller changes and pushes back to the mainline for every major change. Oh, and it's also nice always having the full repository data locally stored.
My requirements for the RCS were: it should be easy to use (no steep learning curve), well tested and somewhat mainstream. BZR fits quite well, especially since Ubuntu heavily relies on it for their launchpad stuff.
PS: Thanks to the alioth team for creating the BZR repository so quickly, it just took like 1 minute.