Detect & clean up messages inconsistent with flags
Bug #319153 reported by
Jeroen T. Vermeulen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Jeroen T. Vermeulen |
Bug Description
Bug 317578 shows how message translations can end up being inconsistent with their flags, so that neither gettext nor Launchpad would accept them the way they are.
Besides catching that situation, we should also be able to clean up the cases where this has happened.
Changed in rosetta: | |
assignee: | nobody → jtv |
importance: | Undecided → High |
milestone: | none → 2.2.1 |
status: | New → In Progress |
Changed in rosetta: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
The attached branch re-checks messages in Hardy and later for gettext errors when given the selection clause:
is_current IS TRUE AND id >= 74539159 AND EXISTS ( .sequence > 0 AND age.potmsgset AND
SELECT * FROM POTMsgSet
WHERE
POTMsgSet
POTMsgSet.id = TranslationMess
flagscomment LIKE '%format%'
)
Took just under 6 hours on staging, of which about 24 minutes were spent collecting the TranslationMess ages. It may be advisable to break it down into chunks.