Stop Bazaar (bzr) from creating .moved files

You have conflicts in some filenames: either you have an unversioned foo in your tree, or you drag and drop a revision where foo becomes a version, or you added foo to two different branches independently and therefore each copy of foo is assigned a different file ID. Therefore, Bazaar tries to keep your files there and not overwrite existing files. In the first case, you have a secure backup tool from bzr, and foo.moved can be removed. But in the second case, you have a real conflict, and you should at least check both foo and foo.moved and resolve the conflict with bzr resolve foo

and then remove foo.moved if necessary.

As such, the strategy for avoiding .moved files largely depends on the reason why they appear in your tree.