lp scheme should suggest launchpad-login for private projects
Bug #229684 reported by
Marc Tardif
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
There have already been bugs reported about pushing projects using the lp: scheme. A similar but less encountered problem is when branching private projects. By default, bzr falls back to http which fails because private projects need authentication for branching. So, it would be nice to inform users about launchpad-login in this circumstance as well.
This problem might be fixed already, I'm using Bazaar (bzr) 1.2.0.
Revision history for this message
| James Westby (james-w) wrote | #1 |
| Changed in bzr: | |
| importance: | Undecided → Wishlist |
| status: | New → Confirmed |
| tags: | added: lp-login lpurl |
| tags: | added: check-for-breezy |
To post a comment you must log in.
Hi,
In newer bzr it will at least warn that the user might not have permission to
do what they want and suggest launchpad-login.
I think it could do better though. I assume the launchpad plugin could
find out if it was a private project, and so refuse the work if launchpad-login
hadn't been run.
There could be information leakage here though, particularly if
private branches of public projects are possible. I don't know how
the web ui handles this.
Thanks,
James