Should tell the user to run bzr launchpad-login before push lp:

[James Westby]

Hi,

This report stems from the message at

https://lists.ubuntu.com/archives/bazaar/2008q1/038160.html

I'm not exactly sure that this is right project for this bug,
so please reassign if I am wrong.

Also I would appreciate any suggestions as to changes
elsewhere we can make to improve this situation.

I'll paste the message here for simplicity

====
Since my new web hotel doesn't support SFTP, I wanted to put bzr
extmerge on launchpad instead. So I created a project, then went to
define "trunk". I got this message

---
You haven't yet told Launchpad where your source code is for External
merge Series: trunk.

If the code is already in a Bazaar branch registered with Launchpad
link the branch to this series.

If the code is in a Bazaar branch not yet on Launchpad you can either:
have the branch mirrored from a remote location by registering a
mirrored branch; or push the branch directly to Launchpad.

You can push a branch to Launchpad for this project with the name
trunk using a command line like:
bzr push lp:~zindar/bzr-extmerge/trunk
---

Ok, so I tried
$ bzr push lp:~zindar/bzr-extmerge/trunk
lp:~zindar/bzr-extmerge/trunk is redirected to
http://bazaar.launchpad.net/~zindar/bzr-extmerge/trunk/
bzr: ERROR: Transport operation not possible: http does not support mkdir()
====

The nasty error message from Bazaar is known, but progress on fixing it
is slow.

This bug report is for the help string suggesting push lp. It caused the
error message here as the user hadn't run bzr launchpad-login first,
so the launchpad plugin didn't know that it could use a bzr+ssh url.

The plugin doesn't know when it is resolving the transport what operation
is being performed, so it can't error at that stage. I think this is difficult
to fix.

Could the message tell the user to unconditionally run bzr launchpad-login?
Would this train the user to do it too much?

We can obviously do better here to help the user get started, and
to avoid driving them away.

Thanks,

James

[Jonathan Lange (jml)]

Users hit this all the time. We need to fix it asap.

[Jonathan Lange (jml)]

I think you are working on this James.

(Thank you so much!)

[Andrew Bennetts (spiv)]

According to the NEWS file, this was fixed by James in bzr 1.4rc1.

[John A Meinel (jameinel)]

Well, the message is a bit verbose at the moment:

bzr log lp:bzr
You have not informed bzr of your launchpad login. If you are attempting a write operation it may fa
il. If it does, run "bzr launchpad-login YOUR_ID" to set your login and try again.

(note, the message was wrapped by my terminal since it is a very long string)

I might recommend that we wrap this to <80 characters, and change the wording to:

You have not informed bzr of your launchpad login. If you are attempting a
write operation and it fails, run "bzr launchpad-login YOUR_ID" and try again.

[Andrew Bennetts (spiv)]

John A Meinel wrote:
[...]
> I might recommend that we wrap this to <80 characters, and change the
> wording to:
>
> You have not informed bzr of your launchpad login. If you are attempting a
> write operation and it fails, run "bzr launchpad-login YOUR_ID" and try again.

That wording looks fine to me. bb:approve ;)

-Andrew.