permission denied push error message is confusing
Bug #736204 reported by
Jeff Hill
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
It seems that only certain paths are allowed when publishing a branch at launchpad. That's fine, but perhaps the resulting "Permission denied" error message is a bit confusing for the uninitiated.
>bzr push lp:~johill-lanl/epics-base/R3.15/ca-ref-man-maint
Connected (version 2.0, client Twisted)
Authentication (publickey) successful!
Secsh channel 1 opened.
bzr: ERROR: Permission denied: "~johill-
>bzr push lp:~johill-lanl/epics-base/ca-ref-man-maint
Connected (version 2.0, client Twisted)
Authentication (publickey) successful!
Secsh channel 1 opened.
Created new stacked branch referring to /~epics-
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| affects: | launchpad → account-plugin-github |
| affects: | account-plugin-github → launchpad |
To post a comment you must log in.
This is a problem for the server, Launchpad, rather than the client, so reassigning.
Launchpad already emits more helpful messages for permission denied in some other cases (e.g. try pushing to a branch like ~/no-such-