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 of Subversion installed, bzr-svn can
23
use passwords cached by Subversion or credentials specified in the URL.
25
Subversion can be forced to cache the password by accessing the repository
26
using the Subversion command-line client.
27
For example, try running 'svn info <url>'.
29
You can specify the username and password in the URL in the standard way, e.g.::
31
$ bzr co svn+http://guest:@tortoisesvn.tigris.org/svn/tortoisesvn/trunk
33
If you are using a Subversion repository over http or https it may be
34
necessary to prefix the repository URL with "svn+", e.g.
35
svn+http://svn.python.org/projects/python/trunk/
37
6
Trying to branch into repository gives an error about incompatibility.
38
7
----------------------------------------------------------------------
39
8
Creating a repository and then trying to clone a Subversion branch into
51
$ bzr upgrade --rich-root-pack
53
Pushing a branch that didn't exist in Subversion yet with `bzr push` fails.
54
---------------------------------------------------------------------------
55
At the moment, only `bzr svn-push` can be used to push new branches into
56
Subversion. Future releases will include this functionality in `bzr push`.
58
More information can be found in the bug report at:
59
https://bugs.launchpad.net/bzr-svn/+bug/127945.
20
$ bzr upgrade --1.9-rich-root
61
22
Cloning a large Subversion branch is very slow
62
23
----------------------------------------------
63
24
There is no way around this at the moment, because Bazaar has to import all
64
the history from the Subversion branch as it doesn't support so-called
67
More information about history horizons can be found at:
68
http://bazaar-vcs.org/HistoryHorizon
25
the history from the Subversion branch.
27
bzr-svn will work significantly faster against a Subversion 1.5 server, so if
28
you have control over the server it may be worthwhile to upgrade it.
30
Alternatively, you may want to just check out the tip of the Subversion branch
31
and access the earlier revisions only when necessary by using stacked branches,
34
$ bzr branch --stacked svn://svn.gnome.org/svn/gnome-specimen/trunk
70
36
The Bazaar revno's differ from the Subversion revno's
71
37
-----------------------------------------------------
72
That's right. Bazaar revision numbers are per-branch, whereas Subversion revno's are per-repository. If you
73
would like to use Subversion revision numbers, use the "svn:" revision specifier. For example:
38
That's right. Bazaar revision numbers are per-branch, whereas Subversion
39
revno's are per-repository. If you would like to use Subversion revision
40
numbers, use the "svn:" revision specifier. For example:
77
44
$ bzr ls -rsvn:34 svn://example.com/bar
79
After upgrading bzr-svn, Bazaar reports branches have diverged while pulling, when they haven't
80
-----------------------------------------------------------------------------------------------
81
As of version 0.4, bzr-svn creates revisions with different revision ids than
82
previous versions. In other words, existing bzr-svn branches created with
83
0.3.x can not be used directly with 0.4.0 but will have to be upgraded to
84
work with 0.4.0 using the "bzr svn-upgrade" command. The bzr-rebase package
85
has to be installed for this command to work correctly.
46
bzr log will also show the Subversion revision number.
87
48
Is it possible to keep the author name when pushing changes into Subversion?
88
49
----------------------------------------------------------------------------
92
53
more information about how to do this.
94
55
You also need to enable support for this in bzr-svn by setting
95
``override-svn-revprops`` to True in ~/.bazaar/bazaar.conf.
97
I converted my Subversion repository using svn-import, but now all branches are empty!
98
--------------------------------------------------------------------------------------
56
``override-svn-revprops`` in ~/.bazaar/bazaar.conf to a comma-separated
57
list of Subversion revision properties you would like to override.
61
override-svn-revprops = svn:log, svn:author
63
Converted a Subversion repository using svn-import leaves all branches empty
64
----------------------------------------------------------------------------
100
66
bzr-svn does not create working trees by default. If you need
101
67
the working trees, run "bzr checkout" in the branch or
104
70
bzr-svn did a replace operation on the branch I pushed to when I tried to push a merge commit to Subversion
105
71
-----------------------------------------------------------------------------------------------------------
106
Yes, this is because bzr-svn has to preserve the mainline history of your
72
Yes, this is because bzr-svn has to preserve the mainline history of your Bazaar
109
75
If you would like to avoid this, use a checkout and merge into that ("bzr co")
110
or rebase on trunk rather than merge it.
76
or rebase on trunk rather than merging it.
120
86
All changes applied successfully.
121
87
Pushed up to revision 1075.
123
If you would like to forbid Bazaar from ever doing these operations, set the
124
``append-revisions-only`` setting to True for the repository you're
89
If you would like to forbid Bazaar from ever doing these replace operations, set the
90
``append_revisions_only`` setting to True for the repository you're
127
93
bzr-svn sets all kinds of file properties when pushing revisions into Subversion. Is this really necessary?
128
94
-----------------------------------------------------------------------------------------------------------
129
Yes, this is because bzr-svn actually supports pushing to Subversion
130
retaining the exact same history that is in the Bazaar branch
131
you're pushing. These properties are used for storing Bazaar metadata that
132
can not be losslessly mapped to existing Subversion metadata.
134
It would be possible to support pushing changes to Subversion without
135
setting that metadata but then the revision created in Subversion
136
would actually be a different one than in your local branch.
95
Yes, this is because bzr-svn pushes to Subversion while retaining the exact
96
same history that is in the Bazaar branch you're pushing.
98
These properties are used for storing Bazaar metadata that can not be
99
losslessly mapped to existing Subversion metadata.
101
bzr-svn can and will use revision properties rather than file properties
102
if the Subversion server is running Subversion 1.5 or higher. These custom
103
revision properties don't show up in commit notifications or trac.
105
Alternatively, it is possible to push changes to Subversion without
106
setting that metadata by using the ``bzr dpush`` command.
107
Since revisions created in Subversion this way are actually (slightly)
108
different from the matching revisions in the local branch, it is necessary for
109
the dpush command to rebase your branch to the remote branch after pushing.
137
111
You would get a DivergedBranches error when pulling from a svn branch you have
140
We have considered setting revision properties with this metadata
141
rather than file properties so they don't show up in "svn diff" but
142
that requires more work in bzr-svn. Being able to set custom revision
143
properties also depends on Subversion 1.5 on the server or modification of the
144
default repository hooks.
146
114
If you are using trac, you can get it to ignore these file properties by
147
setting the "hide_properties" setting in the browser section of your
115
setting the ``hide_properties`` setting in the browser section of your
148
116
configuration to a list of properties that should not be displayed by trac,
154
122
Is it possible to not use the on-disk cache?
155
123
--------------------------------------------
157
Yes, simply set "use-cache = False" for the repository in question in ~/.bazaar/subversion.conf.
158
This will of course have some consequences for the performance of bzr-svn since it
159
will have to re-fetch data.
125
Yes, simply set ``use-cache = False`` for the repository in question in
126
~/.bazaar/subversion.conf. This will of course have some consequences for the
127
performance of bzr-svn since it will have to re-fetch data.
added
removed
FAQ
