OOPS when processing a merge directive with non-launchpad target branch

Bug #309491 reported by Francis J. Lacoste
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Paul Hummer

Bug Description

I tried bzr lpsend on a lazr-js branch.

I received an OOPS reply as OOPS-1083CEMAIL16.

It seems to be caused by the fact that I was missing a submit_branch and public_branch information for the trunk.

The exception is NonLaunchpadTarget

description: updated
Paul Hummer (rockstar)
Changed in launchpad-bazaar:
importance: Undecided → High
status: New → Triaged
Revision history for this message
Paul Hummer (rockstar) wrote :

A also generated a similar oops over the holiday

  https://devpad.canonical.com/~matsubara/oops.cgi/2009-01-02/CEMAIL3

Basically, I branched a project that I needed for a dependency, fixed a bug in it, and then did bzr send on it. I hadn't set it up for submissien. I think it would be good if I got an error email that basically said "I don't know what submit branch you're talking about!" Obviously, my paraphrasing will have to Revelle-ized.

Aaron Bentley (abentley)
tags: added: code-review
Aaron Bentley (abentley)
summary: - OOPS when using bzr send to create a merge proposal with incomplete
- configuration
+ OOPS when processing a merge directive with non-launchpad target branch
Aaron Bentley (abentley)
Changed in launchpad-code:
assignee: nobody → Aaron Bentley (abentley)
Revision history for this message
Aaron Bentley (abentley) wrote :

This has apparently been fixed for ages.

Changed in launchpad-code:
assignee: Aaron Bentley (abentley) → Paul Hummer (rockstar)
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.