1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
|
bzr-svn frequently asked questions
==================================
.. contents::
Bazaar is using a lot of memory accessing a Subversion repository
-----------------------------------------------------------------
bzr-svn can use a lot of memory cloning big branches when older
versions of the python-subversion bindings are used. This memory leak
has been fixed in the trunk of Subversion (r28544) and has been
proposed for inclusion in Subversion 1.4.7.
One way to work around this problem is to Ctrl+C the branch operation
and restart it.
I am unable to access a repository that requires user/password authentication or uses self-signed SSL certificates
------------------------------------------------------------------------------------------------------------------
The Python bindings required for password prompting are only present in
version 1.5 of Subversion so password prompting is only possible if
you have that version installed.
If you have an older version of Subversion installed, bzr-svn can
use passwords cached by Subversion or credentials specified in the URL.
Subversion can be forced to cache the password by accessing the repository
using the Subversion command-line client.
For example, try running 'svn info <url>'.
You can specify the username and password in the URL in the standard way, e.g.::
$ bzr co svn+http://guest:@tortoisesvn.tigris.org/svn/tortoisesvn/trunk
If you are using a Subversion repository over http or https it may be
necessary to prefix the repository URL with "svn+", e.g.
svn+http://svn.python.org/projects/python/trunk/
Trying to branch into repository gives an error about incompatibility.
----------------------------------------------------------------------
Creating a repository and then trying to clone a Subversion branch into
that repository may cause the following error:
::
bzr: ERROR: Repository KnitRepository is not compatible with repository SvnRepository
bzr-svn requires a repository format that supports recording root file ids. To
upgrade the repository, run:
::
$ bzr upgrade --rich-root-pack
Pushing a branch that didn't exist in Subversion yet with `bzr push` fails.
---------------------------------------------------------------------------
At the moment, only `bzr svn-push` can be used to push new branches into
Subversion. Future releases will include this functionality in `bzr push`.
More information can be found in the bug report at:
https://bugs.launchpad.net/bzr-svn/+bug/127945.
Cloning a large Subversion branch is very slow
----------------------------------------------
There is no way around this at the moment, because Bazaar has to import all
the history from the Subversion branch as it doesn't support so-called
history horizons yet.
More information about history horizons can be found at:
http://bazaar-vcs.org/HistoryHorizon
The Bazaar revno's differ from the Subversion revno's
-----------------------------------------------------
That's right. Bazaar revision numbers are per-branch, whereas Subversion revno's are per-repository. If you
would like to use Subversion revision numbers, use the "svn:" revision specifier. For example:
::
$ bzr ls -rsvn:34 svn://example.com/bar
After upgrading bzr-svn, Bazaar reports branches have diverged while pulling, when they haven't
-----------------------------------------------------------------------------------------------
As of version 0.4, bzr-svn creates revisions with different revision ids than
previous versions. In other words, existing bzr-svn branches created with
0.3.x can not be used directly with 0.4.0 but will have to be upgraded to
work with 0.4.0 using the "bzr svn-upgrade" command. The bzr-rebase package
has to be installed for this command to work correctly.
Is it possible to keep the author name when pushing changes into Subversion?
----------------------------------------------------------------------------
Yes, but this requires the repository to allow revision property changes.
See hooks/pre-revprop-change in the Subversion repository for
more information about how to do this.
You also need to enable support for this in bzr-svn by setting
``override-svn-revprops`` to True in ~/.bazaar/bazaar.conf.
I converted my Subversion repository using svn-import, but now all branches are empty!
--------------------------------------------------------------------------------------
bzr-svn does not create working trees by default. If you need
the working trees, run "bzr checkout" in the branch or
specify --trees to svn-import.
bzr-svn did a replace operation on the branch I pushed to when I tried to push a merge commit to Subversion
-----------------------------------------------------------------------------------------------------------
Yes, this is because bzr-svn has to preserve the mainline history of your
branch.
If you would like to avoid this, use a checkout and merge into that ("bzr co")
or rebase on trunk rather than merge it.
For example::
$ bzr push ../trunk
bzr: ERROR: These branches have diverged. Try using "merge" and then "push".
$ bzr rebase ../trunk
All changes applied successfully.
...
$ bzr push ../trunk
All changes applied successfully.
Pushed up to revision 1075.
If you would like to forbid Bazaar from ever doing these operations, set the
``append-revisions-only`` setting to True for the repository you're
pushing to.
bzr-svn sets all kinds of file properties when pushing revisions into Subversion. Is this really necessary?
-----------------------------------------------------------------------------------------------------------
Yes, this is because bzr-svn actually supports pushing to Subversion
retaining the exact same history that is in the Bazaar branch
you're pushing. These properties are used for storing Bazaar metadata that
can not be losslessly mapped to existing Subversion metadata.
It would be possible to support pushing changes to Subversion without
setting that metadata but then the revision created in Subversion
would actually be a different one than in your local branch.
You would get a DivergedBranches error when pulling from a svn branch you have
just pushed to.
We have considered setting revision properties with this metadata
rather than file properties so they don't show up in "svn diff" but
that requires more work in bzr-svn. Being able to set custom revision
properties also depends on Subversion 1.5 on the server or modification of the
default repository hooks.
If you are using trac, you can get it to ignore these file properties by
setting the "hide_properties" setting in the browser section of your
configuration to a list of properties that should not be displayed by trac,
e.g.::
[browser]
hide_properties = svk:merge, bzr:file-ids, bzr:merge, bzr:revision-info
Is it possible to not use the on-disk cache?
--------------------------------------------
Yes, simply set "use-cache = False" for the repository in question in ~/.bazaar/subversion.conf.
This will of course have some consequences for the performance of bzr-svn since it
will have to re-fetch data.
..
vim: ft=rest
|