POTMsgSet merge: yet another unique violation
Bug #403992 reported by
Jeroen T. Vermeulen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Critical
|
Jeroen T. Vermeulen |
Bug Description
When running the message-sharing merge script on elisa, I still see a unique violation during the POTMsgSet merging stage: https:/
A poignant detail is that the unique violation is on a diverged message. That should narrow the search down a little.
Related branches
lp:~jtv/launchpad/cp-bug-403992
Rejected
for merging
into
lp:launchpad/db-devel
- Canonical Launchpad Engineering: Pending requested
- Diff: None lines
lp:~jtv/launchpad/bug-403992
Merged
into
lp:launchpad
- Brad Crittenden (community): Approve
- Diff: None lines
lp:~jtv/launchpad/cp2-bug-403992
Merged
into
lp:launchpad
- Celso Providelo (community): Approve
- Diff: None lines
Changed in rosetta: | |
status: | New → In Progress |
Changed in rosetta: | |
importance: | High → Critical |
Changed in rosetta: | |
status: | In Progress → Fix Committed |
status: | Fix Committed → In Progress |
Changed in rosetta: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The problem is that _saveByDiverging is called, and thinks it can succeed, in a case where diverging actually causes a clash.