Fix TranslationMessage.potemplate links in the database
Bug #299968 reported by
Данило Шеган
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Jeroen T. Vermeulen |
Bug Description
When we forward-copy translations from one distribution series to the new one (eg. we did that for Hardy -> Intrepid around November 10th, and we are going to do that when opening Jaunty), we do not correctly initialise new fields we use for message sharing (i.e. we copy them over as well).
We should set these to NULL and then run our message-
Setting to a milestone just so we don't lose track of it (we should move it as we go along).
Changed in rosetta: | |
importance: | Undecided → High |
milestone: | none → 2.1.12 |
status: | New → Triaged |
Changed in rosetta: | |
milestone: | 2.1.12 → 2.2.1 |
Changed in rosetta: | |
assignee: | nobody → jtv |
Changed in rosetta: | |
milestone: | 2.2.1 → 2.2.2 |
Changed in rosetta: | |
status: | Triaged → In Progress |
Changed in rosetta: | |
milestone: | 2.2.2 → 2.2.3 |
Changed in rosetta: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Run message- sharing- populate script: bug 300664.