1 bzr-svn frequently asked questions
2 ==================================
6 Bazaar is using a lot of memory accessing a Subversion repository
7 -----------------------------------------------------------------
8 bzr-svn can use a lot of memory cloning big branches when older
9 versions of the python-subversion bindings are used. This memory leak
10 has been fixed in the trunk of Subversion (r28544) and has been
11 proposed for inclusion in Subversion 1.4.7.
13 One way to work around this problem is to Ctrl+C the branch operation
16 I am unable to access a repository that requires user/password authentication or uses self-signed SSL certificates
17 ------------------------------------------------------------------------------------------------------------------
18 The Python bindings required for password prompting are only present in
19 version 1.5 of Subversion so password prompting is only possible if
20 you have that version installed.
22 If you have an older version installed, bzr-svn can
23 use passwords cached by Subversion. Subversion can be forced to cache
24 the password by accessing the repository using the Subversion command-line
25 client. For example, try running 'svn info <url>'. If you are using a
26 Subversion repository over http or https it may be necessary to prefix the
27 repository URL with "svn+", e.g.
28 svn+http://svn.python.org/projects/python/trunk/
30 Trying to branch into repository gives an error about incompatibility.
31 ----------------------------------------------------------------------
32 Creating a repository and then trying to clone a Subversion branch into
33 that repository may cause the following error:
37 bzr: ERROR: Repository KnitRepository is not compatible with repository SvnRepository
39 bzr-svn requires a repository format that supports recording root file ids. To
40 upgrade the repository, run:
44 $ bzr upgrade --rich-root-pack
46 Pushing a branch that didn't exist in Subversion yet with `bzr push` fails.
47 ---------------------------------------------------------------------------
48 At the moment, only `bzr svn-push` can be used to push new branches into
49 Subversion. Future releases will include this functionality in `bzr push`.
51 More information can be found in the bug report at:
52 https://bugs.launchpad.net/bzr-svn/+bug/127945.
54 Cloning a large Subversion branch is very slow
55 ----------------------------------------------
56 There is no way around this at the moment, because Bazaar has to import all
57 the history from the Subversion branch as it doesn't support so-called
60 More information about history horizons can be found at:
61 http://bazaar-vcs.org/HistoryHorizon
63 The Bazaar revno's differ from the Subversion revno's
64 -----------------------------------------------------
65 That's right. Bazaar revision numbers are per-branch, whereas Subversion revno's are per-repository. If you
66 would like to use Subversion revision numbers, use the "svn:" revision specifier. For example:
70 $ bzr ls -rsvn:34 svn://example.com/bar
72 After upgrading bzr-svn, Bazaar reports branches have diverged while pulling, when they haven't
73 -----------------------------------------------------------------------------------------------
74 As of version 0.4, bzr-svn creates revisions with different revision ids than
75 previous versions. In other words, existing bzr-svn branches created with
76 0.3.x can not be used directly with 0.4.0 but will have to be upgraded to
77 work with 0.4.0 using the "bzr svn-upgrade" command. The bzr-rebase package
78 has to be installed for this command to work correctly.
80 Is it possible to keep the author name when pushing changes into Subversion?
81 ----------------------------------------------------------------------------
82 Yes, but this requires the repository to allow revision property changes.
84 See hooks/pre-revprop-change in the Subversion repository for
85 more information about how to do this.
87 You also need to enable support for this in bzr-svn by setting
88 ``override-svn-revprops`` to True in ~/.bazaar/bazaar.conf.
90 I converted my Subversion repository using svn-import, but now all branches are empty!
91 --------------------------------------------------------------------------------------
93 bzr-svn does not create working trees by default. If you need
94 the working trees, run "bzr checkout" in the branch or
95 specify --trees to svn-import.
97 bzr-svn did a replace operation on the branch I pushed to when I tried to push a merge commit to Subversion
98 -----------------------------------------------------------------------------------------------------------
99 Yes, this is because bzr-svn has to preserve the mainline history of your
102 If you would like to avoid this, use a checkout and merge into that ("bzr co")
103 or rebase on trunk rather than merge it.
108 bzr: ERROR: These branches have diverged. Try using "merge" and then "push".
109 $ bzr rebase ../trunk
110 All changes applied successfully.
113 All changes applied successfully.
114 Pushed up to revision 1075.
116 If you would like to forbid Bazaar from ever doing these operations, set the
117 ``append-revisions-only`` setting to True for the repository you're