Launchpad itself

authentication (publickey) failed with bzr checkout

Asked by teongleong

My problem is i can no longer do bzr checkout lp:hypedyn anymore
Im on HypeDyn Team which is maintainer of hypedyn so i would expect i would be allowed to check it out.
In fact, I've done it before just a few days ago and was able to do bzr update until I messed it up something but not sure what.

i just recently set up bzr for launchpad
i created my ssh key pairs through the tutorial but i missed out the step whereby i was suppose to download and use Pageant
i did bzr lp-login teongleong successfully which meant (i think) launchpad knows about me and knows i have a public ssh key installed

i realized a problem when i tried to do a bzr commit -m and it throws the following

bzr: ERROR: Cannot lock LockDir(http://bazaar.launchpad.net/~hypedyn-team/hypedy
n/main/.bzr/branch/lock): Transport operation not possible: http does not suppor
t mkdir()

I thought the problem had to do with it starting with http:// instead of the correct bzr+ssh:// so I switched that but I couldn't update anymore and I still couldn't commit. to cut the long story short. i messed around a bit. installed pageant and added the private key file. changed the branch.conf address to a few different variations.

i gave up on the local branch i checked out and tried to checkout a new one with my current setup but I got the following

bzr checkout lp:hypedyn
Connected (version 2.0, client Twisted)
Authentication (publickey) failed.
bzr: ERROR: Connection error: Unable to authenticate to SSH host as
  <email address hidden>
supported auth types: ['publickey']

anyone has any clue on what could be wrong with my set up?

Question information

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

i realized my public key was added wrongly

for some reason 1024 went into the key text and the actual key text went into the comments.

i fixed that. now key text is the long code of text and comment is the text that identifies where you generated the key pair.

i've got a new error message now which i think might have an easy fix somewhere in the forum.

bzr: ERROR: Connection closed: Unexpected end of message. Please check connectiv
ity and permissions, and report a bug if problems persist.

feels like the private key file might not be added properly. i have pageant running and save the private key .ppk file as the tutorial asked. not sure what i missed this time

Revision history for this message
teongleong (teongleong) said : 		#2

I'm very sure i got the public key added correctly this time. somebody can go to my profile and affirm that. my windows machine is using dsa keys now.

and i have pageant open and using the dsa private key file.

my private key file looks correct and it shouldn't be wrong since it is generated by puttygen.

so where else can i go wrong that prevents me from checking out something?

Revision history for this message
teongleong (teongleong) said : 		#3

https://answers.launchpad.net/launchpad/+question/79261

my problem was actually a duplicate of the one above.
after setting up the ssh key pair (public in launchpad and private in pageant), there seemed to be one important environment variable to set in windows

we have to make sure BZR_SSH is set to paramiko for the checking out to start working again.

this time round my check outs correctly put the bzr address with bzr+ssh://

bound_location = bzr+ssh://bazaar.launchpad.net/%2Bbranch/hypedyn/
bound = True

instead of the previous http://

bound_location = http://bazaar.launchpad.net/~hypedyn-team/hypedyn/main/
bound = True

i think it is worth adding this to the current ssh setup faq