Oops when merge directive target branch is not known to Launchpad
Bug #318811 reported by
Aaron Bentley
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Paul Hummer | ||
Bug Description
When creating a merge proposal, if the target branch is not known to LP, an OOPs is generated. Instead, an error should be mailed to the user.
Original report:
Hi! I tried proposing a branch for merge using bzr send --no-bundle, and I got an error email back. It told me to file this question, and reference OOPS-1109CEMAIL10 in the description.
I'm doing this with private branches, dunno if that might have something to do with it. I have things configured as described here: https:/
Also, I did gpg sign my email.
Can you help me get this working?
| Changed in launchpad-bazaar: | |
| assignee: | nobody → rockstar |
| importance: | Undecided → High |
| milestone: | none → 2.2.2 |
| status: | New → Triaged |
| Changed in launchpad-bazaar: | |
| status: | Triaged → In Progress |
Revision history for this message
| Paul Hummer (rockstar) wrote | #1 |
| Changed in launchpad-bazaar: | |
| status: | In Progress → Fix Committed |
| Changed in launchpad-bazaar: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix in rev 7761