+adminpeoplemerge giving bogus error message

Bug #396410 reported by Stuart Bishop
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Unassigned

Bug Description

I need to merge d-filoni into d.filoni. However, the form just gives me a 'constraint not satisfied' error on the duplicated person input (d-filoni). It looks like something is failing and a default error message being used instead. Without this information, I don't know what needs to be fixed.

Stuart Bishop (stub)
Changed in launchpad-registry:
importance: Undecided → Medium
status: New → Triaged
Curtis Hovey (sinzui)
Changed in launchpad-registry:
assignee: nobody → Guilherme Salgado (salgado)
importance: Medium → High
milestone: none → 2.2.7
Revision history for this message
Guilherme Salgado (salgado) wrote : Re: [Bug 396410] [NEW] +adminpeoplemerge giving bogus error message

Did you manage to merge them or is that still pending?

I ask because I could find what we need to change in order to be able to
do the merge while the bug is not fixed.

Revision history for this message
Stuart Bishop (stub) wrote :

On Tue, Jul 7, 2009 at 8:22 PM, Guilherme Salgado<email address hidden> wrote:
> Did you manage to merge them or is that still pending?
>
> I ask because I could find what we need to change in order to be able to
> do the merge while the bug is not fixed.

The merge is still pending.

--
Stuart Bishop <email address hidden>
http://www.stuartbishop.net/

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

For some reason the vocabulary of people that can be merged includes
only people who have at least one email address, and d-filoni doesn't.

I guess this is because the vocabulary used for the duplicated account
on that page is the same one used when non-admins request accounts to be
merged. In the latter case we require an email address because that's
the only way we can confirm the user is who they're claiming to be, but
there's no need for that in +adminpeoplemerge.

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

Since the constraint shouldn't exist, I think it'd be better to lower the importance of this bug and fix the vocabulary. Any objections?

Changed in launchpad-registry:
assignee: Guilherme Salgado (salgado) → nobody
importance: High → Low
milestone: 2.2.7 → none
Revision history for this message
Guilherme Salgado (salgado) wrote :

Can you retry this merge, Stuart? The fix for bug 397148 is now on edge, so it should be possible to do this merge.

Revision history for this message
Stuart Bishop (stub) wrote :

I no longer need to do that merge (the user was happy and closed the question).

This bug report is about getting meaningful error messages on that form instead of 'constraint not satisfied'. We can flag this as wontfix if there is no generic solution (such as using str(exception) as the error message, as this particular case will have been fixed by bug #397148.

Curtis Hovey (sinzui)
tags: added: tech-debt
Curtis Hovey (sinzui)
tags: added: merge-deactivate
Revision history for this message
Curtis Hovey (sinzui) wrote :

The vocabulary was change sometime ago to not require an email address.

Changed in launchpad-registry:
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.