Launchpad itself

My merge proposals are getting OOPS

Asked by John A Meinel

Recently every time I try to review a merge proposal via email, I get an OOPS. The numbers are:

OOPS-1552CEMAIL139
OOPS-1552CEMAIL150
OOPS-1563CEMAIL261
OOPS-1572CEMAIL173
OOPS-1572CEMAIL224
OOPS-1573CEMAIL129
OOPS-1573CEMAIL130

The bottom ones are the most recent, and probably the most relevant. The text in question is something like:

********* *BEGIN ENCRYPTED or SIGNED PART* ********* Vincent Ladeuil wrote:
> > You have been requested to review the proposed merge of lp:~gz/bzr/trivial_smaller_LeafNode into lp:bzr.
> >
> > Minor thing I noticed while looking at something else. The _serialise_key attribute is only assigned to in __init__ so can be moved onto the class. Reduces the __slots__ count on bzrlib.chk_map.LeafNode by one, saving a few bytes per object.
> >
> >

Seems fine to me.

 merge: approve

John
=:->

********** *END ENCRYPTED or SIGNED PART* **********

Does it not like a "merge: ?" without a "review: ?" line? I used to do that all the time.

And, in fact, one of the failures was when doing:
 merge: approve
 review: needsfixing

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Francis J. Lacoste (flacoste) said : 		#1

That's a new bug John, thanks for reporting this. It happens when you approve a branch through email.

Can you help with this problem?

Provide an answer of your own, or ask John A Meinel for more information if necessary.

To post a message you must log in.