This is rather obscure, it may have been fixed in more recent versions though as we encounter some issues with paramiko.
It would be nice if you could try a bare ssh connection to launchpad to ensure you're not encountering an authentication problem there (ssh -v bazaar.launchpad.net should tell you, but on windows it's a bit unclear to ensure that ssh will indeed use the same configuration/login/keys than ssh).
If you're able to push another branch on launchpad, it would be nice to understand what is specific to this failing branch too.
Apart from a weird directory name (as in: using an encoding that is not supported by your filesystem or not recognized by bzr), I fail to see other causes (in addition to a wrong login or no registered ssh keys on launchpad).
This is rather obscure, it may have been fixed in more recent versions though as we encounter some issues with paramiko.
It would be nice if you could try a bare ssh connection to launchpad to ensure you're not encountering an authentication problem there (ssh -v bazaar. launchpad. net should tell you, but on windows it's a bit unclear to ensure that ssh will indeed use the same configuration/ login/keys than ssh).
If you're able to push another branch on launchpad, it would be nice to understand what is specific to this failing branch too.
Apart from a weird directory name (as in: using an encoding that is not supported by your filesystem or not recognized by bzr), I fail to see other causes (in addition to a wrong login or no registered ssh keys on launchpad).