5
Information on how to configure Bazaar.
7
.. TODO: Should have some explanation of why you'd want things in
10
Location of configuration files
11
===============================
12
Each user gets a pair of configurations files in ``$HOME/.bazaar``. The first
13
one, named ``bazaar.conf``, includes default configuration options. The other
14
file, ``locations.conf``, contains configuration information for specific
15
branch locations. These files are sometimes referred to as ``ini files``.
2
=======================
7
While most configuration is handled by configuration files, some options
8
which may be semi-permanent can also be controlled through the environment.
13
Override the email id used by Bazaar. Typical format::
15
"John Doe <jdoe@example.com>"
17
See also the ``email`` configuration option.
22
Override the progress display. Possible values are "none" or "text". If
23
the value is "none" then no progress bar is displayed. The value "text" draws
24
the ordinary command line progress bar.
29
Control whether SIGQUIT behaves normally or invokes a breakin debugger.
31
* 0 = Standard SIGQUIT behavior (normally, exit with a core dump)
32
* 1 = Invoke breakin debugger (default)
37
Override the home directory used by Bazaar.
42
Select a different SSH implementation.
47
Control whether to launch a debugger on error.
49
* 0 = Standard behavior
55
Path to the Bazaar executable to use when using the bzr+ssh protocol.
57
See also the ``bzr_remote_path`` configuration option.
62
Path to the editor Bazaar should use for commit messages, etc.
67
Location of the Bazaar log file. You can check the current location by
68
running ``bzr version``.
70
The log file contains debug information that is useful for diagnosing or
71
reporting problems with Bazaar.
73
Setting this to ``NUL`` on Windows or ``/dev/null`` on other platforms
80
The path to the plugins directory that Bazaar should use.
81
If not set, Bazaar will search for plugins in:
83
* the user specific plugin directory (containing the ``user`` plugins),
85
* the bzrlib directory (containing the ``core`` plugins),
87
* the site specific plugin directory if applicable (containing
88
the ``site`` plugins).
90
If ``BZR_PLUGIN_PATH`` is set in any fashion, it will change the
91
the way the plugin are searched.
93
As for the ``PATH`` variables, if multiple directories are
94
specified in ``BZR_PLUGIN_PATH`` they should be separated by the
95
platform specific appropriate character (':' on Unix,
98
By default if ``BZR_PLUGIN_PATH`` is set, it replaces searching
99
in ``user``. However it will continue to search in ``core`` and
100
``site`` unless they are explicitly removed.
102
If you need to change the order or remove one of these
103
directories, you should use special values:
105
* ``-user``, ``-core``, ``-site`` will remove the corresponding
106
path from the default values,
108
* ``+user``, ``+core``, ``+site`` will add the corresponding path
109
before the remaining default values (and also remove it from
112
Note that the special values 'user', 'core' and 'site' should be
113
used literally, they will be substituted by the corresponding,
114
platform specific, values.
116
The examples below use ':' as the separator, windows users
119
Overriding the default user plugin directory::
121
BZR_PLUGIN_PATH='/path/to/my/other/plugins'
123
Disabling the site directory while retaining the user directory::
125
BZR_PLUGIN_PATH='-site:+user'
127
Disabling all plugins (better achieved with --no-plugins)::
129
BZR_PLUGIN_PATH='-user:-core:-site'
131
Overriding the default site plugin directory::
133
BZR_PLUGIN_PATH='/path/to/my/site/plugins:-site':+user
138
Under special circumstances (mostly when trying to diagnose a
139
bug), it's better to disable a plugin (or several) rather than
140
uninstalling them completely. Such plugins can be specified in
141
the ``BZR_DISABLE_PLUGINS`` environment variable.
143
In that case, ``bzr`` will stop loading the specified plugins and
144
will raise an import error if they are explicitly imported (by
145
another plugin that depends on them for example).
147
Disabling ``myplugin`` and ``yourplugin`` is achieved by::
149
BZR_DISABLE_PLUGINS='myplugin:yourplugin'
154
When adding a new feature or working on a bug in a plugin,
155
developers often need to use a specific version of a given
156
plugin. Since python requires that the directory containing the
157
code is named like the plugin itself this make it impossible to
158
use arbitrary directory names (using a two-level directory scheme
159
is inconvenient). ``BZR_PLUGINS_AT`` allows such directories even
160
if they don't appear in ``BZR_PLUGIN_PATH`` .
162
Plugins specified in this environment variable takes precedence
163
over the ones in ``BZR_PLUGIN_PATH``.
165
The variable specified a list of ``plugin_name@plugin path``,
166
``plugin_name`` being the name of the plugin as it appears in
167
python module paths, ``plugin_path`` being the path to the
168
directory containing the plugin code itself
169
(i.e. ``plugins/myplugin`` not ``plugins``). Use ':' as the list
170
separator, use ';' on windows.
175
Using a specific version of ``myplugin``:
176
``BZR_PLUGINS_AT='myplugin@/home/me/bugfixes/123456-myplugin``
181
The path where Bazaar should look for shell plugin external commands.
184
http_proxy, https_proxy
185
~~~~~~~~~~~~~~~~~~~~~~~
187
Specifies the network proxy for outgoing connections, for example::
189
http_proxy=http://proxy.example.com:3128/
190
https_proxy=http://proxy.example.com:3128/
199
Configuration files are located in ``$HOME/.bazaar`` on Unix and
200
``C:\Documents and Settings\<username>\Application Data\Bazaar\2.0`` on
201
Windows. (You can check the location for your system by using
204
There are three primary configuration files in this location:
206
* ``bazaar.conf`` describes default configuration options,
208
* ``locations.conf`` describes configuration information for
209
specific branch locations,
211
* ``authentication.conf`` describes credential information for
17
214
Each branch can also contain a configuration file that sets values specific
18
215
to that branch. This file is found at ``.bzr/branch/branch.conf`` within the
90
295
With this configuration, the push location for ``/top/location/branch1``
91
296
would be ``sftp://example.com/location/branch1``.
298
Section local options
299
^^^^^^^^^^^^^^^^^^^^^
301
Some options are defined automatically inside a given section and can be
302
refered to in this section only.
304
For example, the ``appendpath`` policy can be used like this::
306
[/home/vila/src/bzr/bugs]
307
mypush = lp:~vila/bzr
308
mypush:policy=appendpath
310
Using ``relpath`` to achieve the same result is done like this::
312
[/home/vila/src/bzr/bugs]
313
mypush = lp:~vila/bzr/{relpath}
315
In both cases, when used in a directory like
316
``/home/vila/src/bzr/bugs/832013-expand-in-stack`` we'll get::
319
lp:~vila/bzr/832013-expand-in-stack
321
Another such option is ``basename`` which can be used like this::
324
mypush = lp:~vila/bzr/{basename}
326
When used in a directory like
327
``/home/vila/src/bzr/bugs/832013-expand-in-stack`` we'll get::
330
lp:~vila/bzr/832013-expand-in-stack
332
Note that ``basename`` here refers to the base name of ``relpath`` which
333
itself is defined as the relative path between the section name and the
336
Another such option is ``branchname``, which refers to the name of a colocated
337
branch. For non-colocated branches, it behaves like basename. It can be used
340
[/home/vila/src/bzr/bugs]
341
mypush = lp:~vila/bzr/{branchname}
343
When used with a colocated branch named ``832013-expand-in-stack``, we'll get::
346
lp:~vila/bzr/832013-expand-in-stack
348
When an option is local to a Section, it cannot be referred to from option
349
values in any other section from the same ``Store`` nor from any other
94
353
The main configuration file, bazaar.conf
95
----------------------------------------
354
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
97
The main configuration file, ``$HOME/.bazaar/bazaar.conf``, only allows one
98
section called ``[DEFAULT]``. This default section contains the default
356
``bazaar.conf`` allows two sections: ``[DEFAULT]`` and ``[ALIASES]``.
357
The default section contains the default
99
358
configuration options for all branches. The default section can be
100
359
overriden by providing a branch-specific section in ``locations.conf``.
105
364
email = John Doe <jdoe@isp.com>
106
365
editor = /usr/bin/vim
107
check_signatures = check-available
108
366
create_signatures = when-required
110
``$HOME/.bazaar/locations.conf`` allows one to specify overriding settings for a
111
specific branch. The format is almost identical to the default section in
112
bazaar.conf with one significant change: The section header, instead of
113
saying default, will be the path to a branch that you wish to override a
114
value for. The '?' and '*' wildcards are supported::
369
The branch location configuration file, locations.conf
370
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
372
``locations.conf`` allows one to specify overriding settings for
373
a specific branch. The format is almost identical to the default section in
374
bazaar.conf with one significant change: The section header, instead of saying
375
default, will be the path to a branch that you wish to override a value
376
for. The '?' and '*' wildcards are supported::
116
378
[/home/jdoe/branches/nethack]
117
379
email = Nethack Admin <nethack@nethack.com>
119
381
[http://hypothetical.site.com/branches/devel-branch]
120
382
create_signatures = always
121
check_signatures = always
123
[http://bazaar-vcs.org/bzr/*]
124
check_signatures = require
126
Common Variable Options
127
=======================
384
The authentication configuration file, authentication.conf
385
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
387
``authentication.conf`` allows one to specify credentials for
388
remote servers. This can be used for all the supported transports and any part
389
of bzr that requires authentication (smtp for example).
391
The syntax of the file obeys the same rules as the others except for the
392
option policies which don't apply.
394
For more information on the possible uses of the authentication configuration
395
file see :doc:`authentication-help`.
404
A comma-separated list of debugging options to turn on. The same values
405
can be used as with the -D command-line option (see `help global-options`).
412
debug_flags = hpss,evil
131
417
The email address to use when committing a branch. Typically takes the form
134
420
email = Full Name <account@hostname.tld>
138
425
The path of the editor that you wish to use if *bzr commit* is run without
139
426
a commit message. This setting is trumped by the environment variable
140
``$BZR_EDITOR``, and overrides ``$VISUAL`` and ``$EDITOR``.
427
``BZR_EDITOR``, and overrides the ``VISUAL`` and ``EDITOR`` environment
433
The default log format to use. Standard log formats are ``long``, ``short``
434
and ``line``. Additional formats may be provided by plugins. The default
144
Defines the behavior for signatures.
440
Reserved for future use. These options will allow a policy for branches to
147
444
The gnupg signature for revisions must be present and must be valid.
182
499
branches below it.
184
501
gpg_signing_command
186
504
(Default: "gpg"). Which program should be used to sign and check revisions.
189
507
gpg_signing_command = /usr/bin/gnpg
509
The specified command must accept the options "--clearsign" and "-u <email>".
514
(Default: "bzr"). The path to the command that should be used to run the smart
515
server for bzr. This value may only be specified in locations.conf, because:
517
- it's needed before branch.conf is accessible
518
- allowing remote branch.conf files to specify commands would be a security
521
It is overridden by the BZR_REMOTE_PATH environment variable.
193
526
(Default: "localhost"). SMTP server to use when Bazaar needs to send
194
527
email, eg. with ``merge-directive --mail-to``, or the bzr-email plugin.
196
529
smtp_username, smtp_password
197
----------------------------
530
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
198
532
User and password to authenticate to the SMTP server. If smtp_username
199
533
is set, and smtp_password is not, Bazaar will prompt for a password.
200
534
These settings are only needed if the SMTP server requires authentication
540
If set to true, bzr will automatically break locks held by processes from
541
the same machine and user that are no longer alive. Otherwise, it will
542
print a message and you can break the lock manually, if you are satisfied
543
the object is no longer in use.
205
548
A mail client to use for sending merge requests.
206
549
By default, bzr will try to use ``mapi`` on Windows. On other platforms, it
207
550
will try ``xdg-email``. If either of these fails, it will fall back to
210
Supported values are:
553
Supported values for specific clients:
212
:xdg-email: Use xdg-email to run your preferred mail program
213
:mapi: Use your preferred e-mail client on Windows.
555
:claws: Use Claws. This skips a dialog for attaching files.
556
:evolution: Use Evolution.
214
559
:thunderbird: Use Mozilla Thunderbird or Icedove. For Thunderbird/Icedove 1.5,
215
560
this works around some bugs that xdg-email doesn't handle.
216
:evolution: Use Evolution.
562
Supported generic values are:
218
565
:editor: Use your editor to compose the merge request. This also uses
219
566
your commit id, (see ``bzr whoami``), smtp_server and (optionally)
220
567
smtp_username and smtp_password.
568
:mapi: Use your preferred e-mail client on Windows.
569
:xdg-email: Use xdg-email to run your preferred mail program
574
If true (default), repository changes are flushed through the OS buffers
575
to physical disk. This is somewhat slower, but means data should not be
576
lost if the machine crashes. See also dirstate.fdatasync.
225
581
The branch you intend to submit your current work to. This is automatically
226
582
set by ``bzr send``, and is also used by the ``submit:`` revision spec. This
227
583
should usually be set on a per-branch or per-location basis.
231
588
A publically-accessible version of this branch (implying that this version is
232
589
not publically-accessible). Used (and set) by ``bzr send``.
238
These options apply only to branches that use the "experimental-branch6"
239
format. They are usually set in ``.bzr/branch/branch.conf`` automatically, but
240
may be manually set in ``locations.conf`` or ``bazaar.conf``.
594
A list of strings, each string represent a warning that can be emitted by
595
bzr. Mentioning a warning in this list tells bzr to not emit it.
599
* ``format_deprecation``:
600
whether the format deprecation warning is shown on repositories that are
601
using deprecated formats.
606
A format name for the default format used when creating branches. See ``bzr
607
help formats`` for possible values.
616
A Python unicode encoding name for text output from bzr, such as log
617
information. Values include: utf8, cp850, ascii, iso-8859-1. The default
618
is the terminal encoding prefered by the operating system.
621
Branch type specific options
622
----------------------------
624
These options apply only to branches that use the ``dirstate-tags`` or
626
are usually set in ``.bzr/branch/branch.conf`` automatically, but may be
627
manually set in ``locations.conf`` or ``bazaar.conf``.
242
629
append_revisions_only
243
---------------------
630
~~~~~~~~~~~~~~~~~~~~~
244
632
If set to "True" then revisions can only be appended to the log, not
245
removed. A branch with this setting enabled can only pull from
246
another branch if the other branch's log is a longer version of its
247
own. This is normally set by ``bzr init --append-revisions-only``.
633
removed. A branch with this setting enabled can only pull from another
634
branch if the other branch's log is a longer version of its own. This is
635
normally set by ``bzr init --append-revisions-only``. If you set it
636
manually, use either 'True' or 'False' (case-sensitive) to maintain
637
compatibility with previous bzr versions (older than 2.2).
251
If present, the location of the default branch for pull or merge.
252
This option is normally set by ``pull --remember`` or ``merge
642
If present, the location of the default branch for pull or merge. This option
643
is normally set when creating a branch, the first ``pull`` or by ``pull
257
649
If present, the location of the default branch for push. This option
258
is normally set by ``push --remember``.
650
is normally set by the first ``push`` or ``push --remember``.
655
If present, defines the ``--strict`` option default value for checking
656
uncommitted changes before pushing.
661
If present, defines the ``--strict`` option default value for checking
662
uncommitted changes before pushing into a different VCS without any
262
668
The location that commits should go to when acting as a checkout.
263
669
This option is normally set by ``bind``.
267
674
If set to "True", the branch should act as a checkout, and push each commit to
268
675
the bound_location. This option is normally set by ``bind``/``unbind``.
680
If present, defines the ``--strict`` option default value for checking
681
uncommitted changes before sending a merge directive.
683
add.maximum_file_size
684
~~~~~~~~~~~~~~~~~~~~~
686
Defines the maximum file size the command line "add" operation will allow
687
in recursive mode, with files larger than this value being skipped. You may
688
specify this value as an integer (in which case it is interpreted as bytes),
689
or you may specify the value using SI units, i.e. 10KB, 20MB, 1G. A value of 0
690
will disable skipping.
698
Defines an external merge tool called <name> with the given command-line.
699
Arguments containing spaces should be quoted using single or double quotes. The
700
executable may omit its path if it can be found on the PATH.
702
The following markers can be used in the command-line to substitute filenames
703
involved in the merge conflict::
709
{this_temp} temp copy of file.THIS, used to overwrite output file if merge
714
bzr.mergetool.kdiff3 = kdiff3 {base} {this} {other} -o {result}
716
Because ``mergetool`` and ``config`` itself both use curly braces as
717
interpolation markers, trying to display the mergetool line results in the
721
$ bzr config bzr.mergetool.kdiff3='kdiff3 {base} {this} {other} -o {result}'
722
$ bzr config bzr.mergetool.kdiff3
723
bzr: ERROR: Option base is not defined while expanding "kdiff3 {base} {this} {other} -o {result}".
725
To avoid this, ``config`` can be instructed not to try expanding variables::
727
$ bzr config --all bzr.mergetool.kdiff3
729
bzr.mergetool.kdiff3 = kdiff3 {base} {this} {other} -o {result}
732
bzr.default_mergetool
733
~~~~~~~~~~~~~~~~~~~~~
735
Specifies which external merge tool (as defined above) should be selected by
736
default in tools such as ``bzr qconflicts``.
740
bzr.default_mergetool = kdiff3
added
removed
bzrlib/help_topics/en/configuration.txt
