Default pqm-submit fails when pushing with bzr+ssh:

[Andrew Bennetts]

As reported by Francis on the launchpad list:

"""
Another limitations of the bzr+ssh push is that we have to
use --public-location sftp://devpad... when using the pqm-submit plugin.
Otherwise, I get the following error:

Command failed!
All lines of log output:
["PQM Cannot merge between different
VCSsystems. 'bzr+ssh://devpad.canonical.com/code/flacoste/launchpad/trivial'(pqm.Baz1_1Handler)
and '/home/pqm/archives/rocketfuel/launchpad/devel'(pqm.Bazaar2Handler) are
different."]

I guess installing 0.12rc1 on PQM would solve that issue.
"""

It appears that PQM needs to be taught to use Bazaar2Handler for "bzr+ssh:" URLs.

In the meantime, a workaround is to specify --public-location, as described by Francis.

[James Henstridge (jamesh)]

Note that using the default push location as a "public location" has been removed in the current version of bzr-pqm (precisely for these sorts of reasons).

You now need to do one of:
 1. pass the public location on the command line
 2. set public_branch for your branch in ~/.bazaar/locations.conf
 3. set public_repository for your repository in ~/.bazaar/locations.conf

[Robert Collins (lifeless)]

pqm does not currently like having multiple aliases to a single target, I'll see about making it do that. Configuring pqm-submit appropriately is probably the best approach for now.

[James Henstridge (jamesh)]

In Bazaar 0.14, it will be easier to configure the push location and PQM public branch once for a tree of branches that get mirrored to the same place using the new config policies feature.

[James Henstridge (jamesh)]

bzr-0.14 is out, and the new appendpath policy lets you configure push_location and public_branch once for all your Launchpad branches, which solves this problem.