Launchpad itself

Merging a not-enabled group with another OOPS's

Bug #316259 reported by Steve McInerney
This bug report is a duplicate of:  Bug #156207: OOPS using +adminteammerge. Edit Remove
10
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned

Bug Description

Reference: https://answers.edge.launchpad.net/launchpad/+question/56726
Am trying to do an adminmerge of '~ubuntu-motu into ~motu'.

~ubuntu-motu is a not enabled group.

The adminmerge failed with OOPS: OOPS-1105ED6

Cheers!
- Steve

See original description
Revision history for this message
Curtis Hovey (sinzui) wrote :

Barry, This appears to have gone belly-up during a mailing list call. Do you have any insights how we can avoid this?

Diogo Matsubara (matsubara)
description: updated
Revision history for this message
Christian Reis (kiko) wrote :

Really? I think the problem is just that the group being merged is not claimed. And I don't think this is a dupe of that bug at least.

Revision history for this message
Christian Reis (kiko) wrote :

And I think that the merging code should be fixed to allow merging unclaimed teams -- it's just a matter of fixing that, right?

Revision history for this message
Guilherme Salgado (salgado) wrote :

This is indeed a dupe; see my last comment on bug 156207.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Related questions

Remote bug watches

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