Bazaar Will Not Let Me Push Revisions

Asked by Jacob MacDonald

For a while, launchpad+bzr was working fine. Then I created a new project - and began to use a new system. As I was going to use the same hostname and username form the new machine, I was careful to delete my existing key so I could begin pushing from the new system. However, bzr did not let me push.

I was able to branch three other projects with no problems. I created a new project, set everything up, and created a new Bazaar repository on my local filesystem. I added a dummy file for the first revision and ran the following commands (after adding a new SSH key):

bzr launchpad-login jaccarmac
bzr push lp:smgenesis

It told me that my publickey was not accepted by launchpad. I tried with several new SSH keys. Then I tried to simply branch the repository. It gave me the same exception.

Any idea why this is not working? What really surprises me is that even branching is rejected by the server.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Jacob MacDonald
Solved:
Last query:
Last reply:
Revision history for this message
Brad Crittenden (bac) said :
#1

You need to upload the public portion of an SSH key to Launchpad and have the private portion properly installed on your machine.

Either retrieve the private portion from your old machine and ensure the public portion is uploaded to Launchpad or simply upload the public portion of one of the new keys you created.

Revision history for this message
Jacob MacDonald (jaccarmac) said :
#2

That is what I did -- several times. I will try again. I think this may have had something to do with the way I was using Bazaar.

Revision history for this message
Brad Crittenden (bac) said :
#3

Jacob I see you now have SSH keys registered. Were you able to push the branch?

Revision history for this message
Jacob MacDonald (jaccarmac) said :
#4

Haven't pushed yet... I'll keep you updated.

Revision history for this message
Jacob MacDonald (jaccarmac) said :
#5

It's working! I'm pretty sure that my problem had something to do with using the seemingly old --use-existing flag for push rather than --use-existing-dir.