Our case is a little different, I think. We have a two PQM instances that need to be able to connect to Launchpad with two different user ids. We do this by creating two separate LP accounts, two ssh key pairs, and putting the public key for each as appropriate. We then specify both IdentityFiles in .ssh/config for bazaar.launchpad.net and as a result our branch locations have to be sftp://{username}@bazaar.launchpad.net/~{team/person}/{project}/{branch} to allow the PQM user to be able to commit to the appropriate branch. Since PQM requires the submit_branch in .bazaar/locations.conf to match the location in the PQM config in published_at, we have to include the {username} portion in .bazaar/locations.conf of the appropriate user that PQM will connect to LP as. And obviously, each user that's submitting to PQM doesn't have access to that account, so the bzr-pqm plugin fails.
Let us know if there's a better/other way of approaching this.
Our case is a little different, I think. We have a two PQM instances that need to be able to connect to Launchpad with two different user ids. We do this by creating two separate LP accounts, two ssh key pairs, and putting the public key for each as appropriate. We then specify both IdentityFiles in .ssh/config for bazaar. launchpad. net and as a result our branch locations have to be sftp://{username} @bazaar. launchpad. net/~{team/ person} /{project} /{branch} to allow the PQM user to be able to commit to the appropriate branch. Since PQM requires the submit_branch in .bazaar/ locations. conf to match the location in the PQM config in published_at, we have to include the {username} portion in .bazaar/ locations. conf of the appropriate user that PQM will connect to LP as. And obviously, each user that's submitting to PQM doesn't have access to that account, so the bzr-pqm plugin fails.
Let us know if there's a better/other way of approaching this.