no lp-logout command

That's true. As a workaround, they can edit ~/.bazaar/bazaar.conf

(02:32:48) RenatoSilva: bzr branch lp:bzr-email: FATAL ERROR: Disconnected: No supported authentication methods available
(02:33:12) RenatoSilva: can't I branch as anonymous after a lp-login?
(02:39:21) jmarsden: RenatoSilva: I think you can't "undo" the lp-login easily, you have to edit or rm a file or two under .bzr/ before it will use http to access the repository. Someone was discussing this eitehr here on on #ubuntu-motu a few days ago I think.
jmarsden jml
(02:39:57) RenatoSilva: jmarsden: thanks for the info at least
(02:40:34) RenatoSilva: jmarsden: something like bzr branch --annonymous, and bzr lp-logout would be nice

This is _essential_ for people who use the Arch Linux distribution and are members of a Launchpad project; it becomes impossible to build -bzr PKGBUILDs when you're logged into Launchpad. This happens: http://omploader.org/vNHIzZw

The mentioned workaround works, but it is far from ideal.

Trent I'm not really sure why that's related, can you please post the
traceback from .bzr.log?

How come this bug is lower priority than its duplicate, #438711 ?

On 11 February 2011 11:32, Robert Collins <email address hidden> wrote:
> ** Changed in: launchpad
>       Status: New => Invalid

Sam, this doesn't require any code changes in Launchpad.

Another workaround, available in bzr >= 2.3:

  bzr config --remove launchpad_username

Why does a read-only command like "bzr branch" use the login info at all?

On 4 April 2011 23:43, Beni Cherniavsky <email address hidden> wrote:
> Why does a read-only command like "bzr branch" use the login info at
> all?

Because it uses the login info to create an ssh connection, and then
it branches over that. That's a bit faster and a bit less prone to
interference from http proxies or other causes.

And it works for private branches.

I just got bit by this bug. Had to track down this report to get a solution, then had to figure out where the config file is stored on Windows to fix it. I would recommend that if read-only operations such as pull should fail due to SSH connection issues, then simply print a warning and attempt to fall back to HTTP.