Launchpad itself

Error when sending mail to a code review for source package branch

Bug #426779 reported by James Westby
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Aaron Bentley
Launchpad itself 3.0

Bug Description

Hi,

I got OOPS-1348CEMAIL2 in response to a seemingly innocuous email
to mp+11231.

Thanks,

James

Revision history for this message
Aaron Bentley (abentley) wrote : Re: [Bug 426779] [NEW] Error when sending mail to a code review for source package branch

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

James Westby wrote:
> Public bug reported:
>
> Hi,
>
> I got OOPS-1348CEMAIL2 in response to a seemingly innocuous email
> to mp+11231.

We don't have the right database permissions set for branch merge
proposals on package branches.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkqnrx8ACgkQ0F+nu1YWqI3AogCeNqLRjX4sKCyOVzfF1yZzxHYO
Ho8AnA55XfEvaH8IJQ1Mkq14/YbHN9ca
=aNh6
-----END PGP SIGNATURE-----

Revision history for this message
James Westby (james-w) wrote :

Hi,

I would consider this highly important for Ubuntu's use of code review,
as I suspect that the email interface will be widely used, and getting
a failure email every time you email a merge proposal will get tedious
very quickly.

Thanks,

James

tags: added: package-branches
Revision history for this message
Aaron Bentley (abentley) wrote :

I am currently pushing up a branch that fixes this. I expect the problem will be fixed with the 3.0 release.

Revision history for this message
James Westby (james-w) wrote : Re: [Bug 426779] Re: Error when sending mail to a code review for source package branch

On Wed Sep 09 16:32:34 UTC 2009 Aaron Bentley wrote:
> I am currently pushing up a branch that fixes this. I expect the
> problem will be fixed with the 3.0 release.

Perfect, thank you.

James

Revision history for this message
James Westby (james-w) wrote :

Hi,

Thanks for getting this merged, what should the status be set to? Do
you milestone all fixes for release tracking?

Thanks,

James

Aaron Bentley (abentley)
Changed in launchpad-code:
status: New → Fix Committed
milestone: none → 3.0
Tim Penhey (thumper)
Changed in launchpad-code:
assignee: nobody → Aaron Bentley (abentley)
importance: Undecided → High
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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