How to work with bazaar through the GUI on Windows

Alternative: use Bazaar from the command line

If the GUI is not your prefered way of doing things, please see How to work with bazaar on the command line

Download Bazaar for Windows

You find the downloads for Bazaar for Windows here: http://wiki.bazaar.canonical.com/WindowsDownloads

We currently recommend to use the Standalone 2.4 Stable Release. This includes the core Bazaar distribution and several GUIs for Bazaar.

We have noticed that the german translation is not complete at all, and on German Windows systems the GUI is quite mixed up with several languages. Solution: delete all but the en locale directory from C:\Program Files\Bazaar\locale. If the local-folder is not available on your computer you can also set the LANG environment variable to the required language code.

See also Visual Tour of Bazaar Explorer on Windows.

If you still get plink console windows with bazaar, have a look those instructions!

Setup your environment

Start Bazaar Explorer from the Start menu.

Go to Settings|Configuration|User Configuration to set your user name and email address:

Set up the bug tracker integration as follows:

Here is the URL for easy copy&paste: http://sourceforge.net/apps/mantisbt/openpetraorg/view.php?id={id}

The commit dialogue of Bazaar Explorer allows one to specify a bug that was closed with the commit. One needs to prefix the bug number with 'op:' (e.g. 'op:170' if Bug #170 is closed in the openPETRA bug tracker).

If you prefer to use WinMerge for showing the diff of files, you can configure it in the same window as well:

To setup KDiff3 (http://kdiff3.sourceforge.net/) as your Merge tool, configure it in the same window:

For Copy&Paste: "C:\Program Files (x86)\KDiff3\kdiff3.exe" --output "%r" "%b" "%t" "%o"

Now you should configure a directory where you will store all your branches. Go to "Start a new project", and click on "Initialize". Make sure to select the options "Shared repository" and "Branches in the repository will default to not having a working tree".

I have chosen the directory <My Documents>/openpetra/bzr/

Especially when using Windows 7 it is recommended to create the repository in a local directory (e.g. on C:) and not one on the network as otherwise compiling with NAnt can give problems. Compiling from a network drive gave the following error on Windows 7:

System.Security.SecurityException: Request for the permission of type 'System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, ... failed

You might be asked, if you want to create a new "hat". Just say yes. An explanation can be found here: http://wiki.bazaar.canonical.com/BzrExplorer#hats

Line Ending issues

To avoid problems with the line endings, and the code generators, in Bazaar Explorer go to Settings/Rules and insert the content listed at How_to_work_with_bazaar_on_the_command_line#Line_Ending_issues

See also http://doc.bazaar.canonical.com/development/en/user-reference/eol-help.html

Working with trunk and branches in Bazaar

trunk is the main branch of the repository. Only members of the core development team can commit to trunk and merge changes from a branch into trunk.

For other developers it still might make sense to checkout trunk, for readonly access, and to compile the latest version from the repository.

Every developer needs to create a free account at http://launchpad.net, for hosting their own branches there.

For the core developers, that have write access to trunk, we have agreed to create an extra branch for each bug or feature from Mantis, that takes more than 3 hours to develop, including the time needed for coding and testing. Only small bugs and not so complicated fixes can be committed directly into trunk.

There are several options how the local repository looks like. With a shared repository as described above in the setup of the working environment, you can check out several branches (and trunk which is just a special branch) into separate working trees.

Create your own branch

For creating a new branch, you need to follow these steps:

Setup your Launchpad account

You only need to do this once!

1. First get an account on Launchpad, which is a service provided by the company Canonical, who develop Ubuntu and Bazaar: https://login.launchpad.net/+new_account
2. Create a public and private key on launchpad. This is explained here. It is quite important to execute pageant and to load the private key into pageant.
3. In your bazaar, you need to tell your launchpad username. You can do this in the GUI as well, in the menu Bazaar / All Commands / category Launchpad, Command launchpad-login, and enter your launchpad id as the parameter.

Create a new branch on Launchpad

Login to Launchpad, and then go to https://code.launchpad.net/openpetraorg/+addbranch.

The new branch will have the url lp:~USERNAME/openpetraorg/BRANCH_NAME

Create a branch at Launchpad

Checkout the code into a working tree

You can download the trunk or any other branch into your own directory, by selecting in the menu Bazaar | Start | Checkout.

Please always use this source URL:

lp:openpetraorg

Make sure you have started pageant with your private key, otherwise your connection to the bazaar server will fail. To do that, you just need to double-click on the .ppk file, which is the private key file which you saved when you created the SSH key for developer access.

For just browsing the source online, go to

http://code.openpetra.org

The destination for the checked out trunk would be in my case:

<My Documents>/openpetra/bzr/work

Please make sure that the destination is inside your repository directory which you have created earlier! Avoid network drives as mentioned above!

After the checkout has finished, click on Refresh in the Bazaar Explorer, and then double-click trunk to get to the view of the current working tree:

Switch your working tree to your branch

• Click the 'Switch' Button in the ToolBar.
• You need to specify the name of the branch on the bazaar server.
• Our naming convention for branches is to use dev_0000<Mantis Issue number>_<keywords to describe the issue>

In this example it is: bzr+ssh://bazaar@bzr.openpetra.org:2208/openpetra/dev_0000167_import_cc_hierarchy/

In the end, your code will still be in My Documents\openpetra\bzr\work, but if you commit, it will always be against bzr+ssh://bazaar@bzr.openpetra.org:2208/openpetra/dev_0000167_import_cc_hierarchy/, and the title of the Bazaar Explorer window also contains the name of the branch you are working with.

To get an overview of all the existing Branches of openpetra go to this website.

Commit added and modified files

The Bazaar Explorer should look similar to this for your working tree:

This screen gives you access to operations like:

• Add: add new files
• Rename: rename files in the working tree control
• Commit: commit local changes to the repository.
  • Please enter the Mantis numbers of the bugs you have fixed (in edit field Fixed bugs), in the format op:<mantis number>, eg. op:123 op:124
  • it is recommended always to commit to the central repository, and to avoid local commits

Alternatively, you can work with Tortoise Bazaar as well:

Rebase a branch

You should rebase your branch regularly, so that the changes happening in trunk are flowing back into your branch.

You need to click on Merge, and if there have been changes merged into your branch, you will need to Commit as well.

It is highly recommended to first commit all your own local changes, before doing a merge.

Merge to trunk

You need to switch to trunk, and then do a Merge from the branch. Resolve conflicts if there are any, and do a Commit.

Resolve conflicts

This example will show you how to resolve a conflict.

The situation: the file Gift.Importing.cs has been edited both in trunk and in the dev branch. We switch to the dev branch, and select Merge from bzr+ssh://bazaar@bzr.openpetra.org:2208/openpetra/trunk/

This is how it looks in Bazaar Explorer:

Now go in the menu to Bazaar > Work > Resolve Conflicts. You will get this screen:

If you have configured KDiff3 right, you should be able to double-click the conflict files and see them in KDiff3. This only works for files that have text conflicts. For files with content conflicts, you need to manually compare the .BASE and .THIS or .OTHER file with the current file.

In KDiff3, you have 3 columns:

• The left column (A) is the BASE version. This is the version before all changes happened, the common source of the branches.
• The center column (B) is the THIS version. This is the version that you have last had in your branch.
• The right column (C) is the OTHER version. This is the version coming from trunk, in our example.
• The file at the bottom is the resulting file. You can go through the conflicts, and select if you want to select the version from A, B, or C, or you can modify it yourself.

Make sure that the line end style is set to DOS (and not to UNIX).

You might also want to right click the conflicting file in the Explorer, and select the Log, this will you to see what happened to the file, and how the changes got into that file, by looking at the diff of each commit.

After you have fixed the bottom file, saved it and closed KDiff3, select "Mark as resolved" in the conflicts list window, when right-clicking the conflict file.

Frequently asked questions

bzr: ERROR: Could not acquire lock (remote lock)

This can happen when cancelling during a commit, and probably in other situations too. You will get the error the next time your are attempting to commit.

Solution: open the command line console (eg. cmd.exe), and change into the directory of your branch, and run:

bzr break-lock