Q: authentication.conf not using 'user' attribute?

[Maritza Mendez]

I think its debatable whether the form of thee scheme is documented or
just incidentally discoverable.  That's why I tried all three
"logical" forms.

The main problem is that bzr apparently does not detect paramiko and
requires the BZR_SSH envvar.  Now that was not obvious in the docs for
authentication.conf (Thanks Alex!).

My new problem is that paramiko does not seem to like my rsa keypair
and bzr then falls back to openssh.  Maybe I need to gen a new
keypair...

when I get it working I will file a bug with suggested changes to docs.

Thanks
~M



On 8/21/10, Vincent Ladeuil <v.ladeuil+lp at free.fr> wrote:
>>>>>> Maritza Mendez <martitzam at gmail.com> writes:
>
> <snip/>
>
>     > I have it set up on the local machine with authentication.conf like
> this:
>
>     > [server.org]
>     > scheme=bzr+ssh
>
> Every protocol using ssh should use the 'ssh' scheme, so bzr+shh and
> sftp.
>
> You're not the first one to fall into this trap (even if it's
> documented) which clearly hints that bzr should certainly accept all of
> them as valid synomyns (and maybe issue a warning).
>
> Care to file a bug for that ?
>
>     > host=server.org
>     > user=bzruser
>     > password=password_for_user=bzrusr_on_server.org
>
> Is that double '=' intended ?
>
>     > But when I say
>
>     > bzr branch bzr+ssh://server.org/path/to/trunk
>
>     > I am *always* prompted for the password of == the user running the
> command
>     > on the local machine == which of course is not bzruser (and actually
> does
>     > not match any username on server.org)
>
>     > It's as if bzr is not using (or not finding a match to server.org)
>     > in authentication.conf.  So I tried changing scheme=bzr to
>     > 'bzr+ssh' or just 'ssh' but none of those works either.
>
> That's unexpected, 'ssh' should have worked. Did you try adding '-Dauth'
> to the parameters to get more feedback there ?
>
>        Vincent
>